HIP-4 outcome markets use side identifiers and probability-priced fields.Documentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
mark_price and mid_price represent implied probability in [0, 1], not USD.
HIP-4 REST
Outcome-market route family.
Response schemas
Shared field rules and envelope behavior.
Why 0xArchive Fits
HIP-4 data is easy to misuse if it is treated like a normal perp or Spot market. 0xArchive separates HIP-4 into/v1/hyperliquid/hip4/*, documents the probability-price caveat, and keeps outcome-market routes visible in the REST taxonomy.
Use HIP-4 routes for outcome discovery, side-level order books, trades, candles, open interest, and historical probability analysis where the generated reference exposes the relevant endpoint. Store the outcome identifier, venue family, timestamp, and request ID with every output.
Implementation Pattern
Start by discovering or confirming the outcome side, then pull a small order-book, trade, or candle request. If the output feeds a model, alert, or backtest, check data-quality routes and label price fields as probabilities. If a coding agent generates code, instruct it to preserve# identifiers and URL encoding.