outcomeMeta

Commonly used to enumerate all active HIP-4 binary outcome markets on HyperCore.

POST /info

outcomeMeta

cURL

curl --request POST \
  --url https://hypercore.goldrushdata.com/info \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "<string>"
}
'

200

{
  "outcomes": [
    {
      "outcome": 123,
      "name": "<string>",
      "description": "<string>",
      "sideSpecs": [
        {
          "name": "<string>"
        }
      ]
    }
  ]
}

Credit Cost

1 per call

Processing

Realtime

• Wire-equal to POST api.hyperliquid.xyz/info with {"type": "outcomeMeta"}.
• For real-time price updates on a discovered outcome, subscribe to ohlcvCandlesForPair using the per-side encoding. See the HIP-4 markets recipe for end-to-end discovery and streaming patterns.
• HIP-4 launched on Hyperliquid mainnet on May 2, 2026. Read the canonical spec: 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

cURL

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

Response

{
  "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.

Show 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.

Show properties

name · string

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