> ## Documentation Index
> Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# outcomeMeta | Hyperliquid Info API

> Hyperliquid outcomeMeta: enumerate all active HIP-4 binary outcome markets on HyperCore.

> [card] Credit Cost
>
> 1 per call

> [card] Processing
>
> Realtime

The Hyperliquid info endpoint with `type: "outcomeMeta"` is used to enumerate all active HIP-4 binary outcome markets on HyperCore.

> [!TIP]
>
> Estimate your monthly cost for this API using the [Pricing Calculator](https://goldrush.dev/docs/pricing-calculator.md?endpoint=%2Fapi-reference%2Fhyperliquid-info%2Foutcome-meta).

> [!NOTE]
>
> * Wire-equal to `POST api.hyperliquid.xyz/info` with `{"type": "outcomeMeta"}`.
> * HIP-4 launched on Hyperliquid mainnet on May 2, 2026. Read the canonical spec: [HIP-4: Outcome markets](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-4-outcome-markets).

Returns the live HIP-4 outcome universe: every active binary outcome market on HyperCore with its integer `outcome` ID, human-readable `name`, structured `description`, and `sideSpecs` (Yes / No).

This is a global, non-user-keyed type. A single cache entry is shared across all callers and is refreshed continuously from upstream Hyperliquid.

`outcomeMeta` is HIP-4’s dedicated metadata type - separate from `metaAndAssetCtxs`, which covers perps and spot. Use it to discover live outcome IDs and compute per-side market encodings (`encoding = 10 * outcome + side`) before subscribing to OHLCV or fills.

## Endpoint

```
POST https://hypercore.goldrushdata.com/info
Authorization: Bearer <GOLDRUSH_API_KEY>
Content-Type: application/json
```

## Request

**type** `string` *required*

Always `"outcomeMeta"`.

### Example

```bash cURL theme={null}
curl -X POST https://hypercore.goldrushdata.com/info \
  -H "Authorization: Bearer $GOLDRUSH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "outcomeMeta"
  }'
```

```typescript TypeScript theme={null}
const response = await fetch("https://hypercore.goldrushdata.com/info", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    type: "outcomeMeta",
  }),
});

const { outcomes } = await response.json();
```

```python Python theme={null}
import os, requests

response = requests.post(
    "https://hypercore.goldrushdata.com/info",
    headers={"Authorization": f"Bearer {os.environ['GOLDRUSH_API_KEY']}"},
    json={"type": "outcomeMeta"},
)

outcomes = response.json()["outcomes"]
```

## Response

```json theme={null}
{
  "outcomes": [
    {
      "outcome": 123,
      "name": "Recurring",
      "description": "class:priceBinary|underlying:HYPE|expiry:20260310-1100|targetPrice:34.5|period:3m",
      "sideSpecs": [
        { "name": "Yes" },
        { "name": "No" }
      ]
    }
  ]
}
```

### Field descriptions

**outcomes** `array\<object\>`

Array of active outcome markets.

**properties**

**outcome** `int`

Integer outcome ID. Combine with a side index to compute the tradeable market encoding: `encoding = 10 * outcome + side`. An outcome with `Yes` (side 0) and `No` (side 1) yields two encodings (e.g. `1230` and `1231`).

**name** `string`

Human-readable label for the market - for example, `"Recurring"` for repeating daily/weekly markets.

**description** `string`

Pipe-delimited spec describing the market. Parse it once to extract the full definition:

| Field | Example | Meaning |
| - | - | - |
| `class` | `priceBinary` | Market class (binary outcome on a price threshold). |
| `underlying` | `HYPE` | Asset the outcome resolves against. |
| `expiry` | `20260310-1100` | Resolution timestamp, `YYYYMMDD-HHMM` UTC. |
| `targetPrice` | `34.5` | Threshold the underlying is compared against at expiry. |
| `period` | `3m` | Recurrence cadence for repeating markets. |

**sideSpecs** `array\<object\>`

Tradeable sides of the outcome, ordered by side index. For binary outcomes, index 0 is `Yes` and index 1 is `No`.

**properties**

**name** `string`

Side label - typically `"Yes"` or `"No"` for binary outcomes.

## Related endpoints

> [card] [metaAndAssetCtxs](https://goldrush.dev/docs/api-reference/hyperliquid-info/meta-and-asset-ctxs.md)
>
> fetch the full Hyperliquid perpetuals market universe with live per-asset trading context.

> [card] [spotMetaAndAssetCtxs](https://goldrush.dev/docs/api-reference/hyperliquid-info/spot-meta-and-asset-ctxs.md)
>
> fetch the spot universe metadata, token configuration, and live market data in a single call.

> [card] [meta](https://goldrush.dev/docs/api-reference/hyperliquid-info/meta.md)
>
> fetch the perpetuals universe metadata without live market context.

> [card] [settledOutcome](https://goldrush.dev/docs/api-reference/hyperliquid-info/settled-outcome.md)
>
> retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.

> [card] [spotMeta](https://goldrush.dev/docs/api-reference/hyperliquid-info/spot-meta.md)
>
> fetch the spot universe metadata and full token configuration without live market context.

> [card] [allPerpMetas](https://goldrush.dev/docs/api-reference/hyperliquid-info/all-perp-metas.md)
>
> fetch the perpetuals metadata — universe definitions and margin tables — for every perp DEX in a single request.

See all Hyperliquid endpoints: [Overview hub](https://goldrush.dev/docs/goldrush-hyperliquid/overview.md) · [Info API reference](https://goldrush.dev/docs/goldrush-hyperliquid/info-api/overview.md)

*Last reviewed: 2026-07-23*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.