/v1/hyperliquid/hip4. Its mark_price and mid_price fields are implied probability between 0 and 1, not USD prices, and 0xArchive keeps that interpretation attached to the route and response.
What One Key Returns
Why Teams Choose 0xArchive
HIP-4 is not ordinary price history, and treating it that way corrupts the result. Themark_price and mid_price fields are implied probability between 0 and 1, not USD prices, and a parser that mixes them with spot or perp assumptions produces wrong features. 0xArchive keeps the probability interpretation, outcome IDs, side identifiers, and settlement context attached to the route, the response, and the export schema.
0xArchive returns each HIP-4 data family on its own route so coverage is explicit, not inferred from one successful endpoint. Order books, trades, OI, and order-level (L4) depth are all available since May 2026, with /v1/hyperliquid/hip4/outcomes listing about 554 outcome series so a model feature, dashboard, or settlement study can resolve the exact market first.
Store the request ID when the response exposes it and check freshness before the result feeds research, a dashboard, an export, or generated code.
Order placement, account state, and wallet signing are someone else’s job here, and so is venue breadth beyond HIP-4 outcome markets.
Run One Route
Evaluation Questions
1
Resolve the outcome market
Start with
/v1/hyperliquid/hip4/outcomes to get the outcome ID and side identifier before generating any data call.2
Keep probability prices straight
Treat
mark_price and mid_price as implied probability between 0 and 1, not USD, and keep them attached to the outcome-market context in storage.3
Gate the window
Run a
/v1/hyperliquid/hip4/freshness/{symbol} check before the result feeds research, a dashboard, an export, or generated code.