HIP-4 outcome markets live underDocumentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
/v1/hyperliquid/hip4/*. Use this family when the product needs binary outcome-market data, side-level order books, trades, candles, open interest, or probability-like mark and mid values.
Example
Use HIP-4 For
| Need | Route family |
|---|---|
| Outcome discovery | HIP-4 outcomes and instruments |
| Side-level order book | HIP-4 order-book routes |
| Outcome trades | HIP-4 trade routes |
| Probability history | HIP-4 candles, mark/mid, and open-interest projections |
Implementation Notes
HIP-4 routes are for outcome-market data, so symbol handling and price interpretation are different from core perps or Spot pairs. Store the outcome identifier and venue family with every record. If a UI, model, or backtest displays a HIP-4 price, label it as probability-like market pricing rather than a dollar-denominated asset price. Use outcome discovery before assuming an identifier. Then pull the side-level order book, trades, candles, or open-interest route that matches the workflow. For historical analysis, combine the market-data request with Data Quality and request-ID logging so probability series can be audited later.HIP-4 Request Packet
Use this packet before HIP-4 data enters charts, models, exports, or generated clients.| Field | HIP-4 value |
|---|---|
| Namespace | /v1/hyperliquid/hip4/* |
| Identifier | Outcome ID, side identifier, or symbol from the generated reference |
| Price handling | Treat documented mark and mid values as implied probabilities in [0, 1] |
| First probe | Outcome discovery, one order book, one trades page, or one OI request |
| Stop rule | Do not route outcome IDs through core Hyperliquid, Spot, HIP-3, or Lighter paths |
Implementation Fit
Use HIP-4 when the business question is about outcome markets, not assets. A HIP-4 chart, model feature, alert, or export should preserve outcome id, side id, route family, and probability-price semantics. Use Hyperliquid REST API for normal perps and Hyperliquid Spot for pair markets.Common Mistakes
Do not compare HIP-4mid_price directly with BTC, ETH, or Spot pair prices. Do not route # outcome identifiers through Hyperliquid core or Lighter paths. Do not remove URL encoding from examples such as %230 when building curl commands.