Skip to main content
POST
info (outcomeMeta)
The info endpoint with type: "outcomeMeta" retrieves the live HIP-4 outcome markets, multi-outcome questions, and market deployers on the Hyperliquid exchange. Outcome markets are fully collateralized binary contracts that settle within a fixed range — the primitive that powers prediction markets and bounded options-like instruments on Hyperliquid.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

Parameters

  • type (string, required) — Must be "outcomeMeta"

Returns

Returns an object with four fields: outcomes, questions, deployers, and feeScale.

Outcomes

An array of live outcome markets. Each entry contains:
  • outcome (integer) — Outcome id. Used together with the side index to derive the asset encoding.
  • name (string) — Market name: "Recurring" for recurring binary markets, or the template name (for example, "template:binaryPrice") for markets created by a deployer.
  • description (string) — Pipe-separated key:value string. Recurring binaries carry class, underlying, expiry, targetPrice, and period (for example, "class:priceBinary|underlying:BTC|expiry:20261113-0600|targetPrice:73567|period:1d"). Deployer markets carry their template parameters.
  • sideSpecs (array) — Two-element array describing the YES (index 0) and NO (index 1) sides. Each element has a name field.
  • quoteToken (string) — Token the outcome settles in. Every current market settles in "USDC".
  • venue (string) — Venue of the deployer that created the market. Absent on recurring markets.
  • deployerFeeScale (string) — Fee scale set for a deployer market, as a decimal string. Absent on some markets.

Questions

An array of multi-outcome questions, both recurring (such as the daily BTC price bucket) and created by deployers. Each entry contains:
  • question (integer) — Question id.
  • name (string) — Question text.
  • description (string) — Free-form description.
  • fallbackOutcome (integer) — Outcome id used if none of the named outcomes matches.
  • namedOutcomes (array of integers) — Outcome ids for the named legs.
  • settledNamedOutcomes (array of integers) — Outcome ids that have already settled.

Deployers and fee scale

  • deployers (array) — Market deployers. Each entry has deployer (address), venue (venue name), and subDeployers, a list of [action, [addresses]] pairs naming the accounts a deployer delegates each action to.
  • feeScale (string) — Global outcome market fee scale, as a decimal string.

Asset encoding

outcomeMeta does not return per-side coin strings or asset ids. Compute them client-side from outcome and side (0 for YES, 1 for NO):
For example, YES (side 0) on outcome 1 has the encoding 10, the trade coin #10, the balance coin +10, and the asset id 100_000_010. Recurring markets get a new outcome id for every instance, so read the current id from outcomeMeta rather than hardcoding it. See the full guide at Trading HIP-4 outcome markets on Hyperliquid for the rest of the trading flow.

Example request

Use your own endpoint in your code. The code examples use a placeholder Chainstack endpoint (YOUR_CHAINSTACK_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the Chainstack console. The curl above uses a shared public endpoint for quick checks only; do not use it in production.

Use cases

  • Market discovery — enumerate every live outcome market and its side names before placing orders.
  • Settlement parser — read description to extract the expiry and targetPrice for recurring binary markets, or the template parameters for deployer markets.
  • Multi-outcome markets — list the named legs of a question and their settled status.
  • Inventory reconciliation — track which outcome ids are still live so you can mark settled positions out of your book.

Body

application/json
type
enum<string>
default:outcomeMeta
required

Request type to retrieve HIP-4 outcome market metadata

Available options:
outcomeMeta

Response

200 - application/json

Live HIP-4 outcome markets and categorical questions

outcomes
object[]

Array of live outcome markets

questions
object[]

Array of multi-outcome questions, recurring and deployer-created

deployers
object[]

Market deployers and the accounts they delegate actions to

feeScale
string

Global outcome market fee scale, as a decimal string

Last modified on November 12, 2026