/v1/symbols coverage_by_type. Verify the outcome and symbol through the discovery routes before generating a request. It is not the right fit for ordinary spot or perp price history, order placement, account state, or wallet signing.
HIP-4 is a Hyperliquid-scoped outcome-market family under /v1/hyperliquid/hip4. Its mark_price and mid_price values are implied probabilities from 0 to 1, not USD prices. HIP-4 does not expose funding or liquidation routes in the current route family.
HIP-4 Route Matrix
Why Teams Choose 0xArchive
HIP-4 requires a parser that preserves outcome identity and probability meaning. Treatingmark_price or mid_price as a dollar quote produces the wrong feature, even when the JSON is syntactically valid. 0xArchive keeps outcome IDs, side identifiers, probability-priced fields, and settlement context beside the route and response.
Use the outcome listing or question route first, then request the selected symbol. Save meta.request_id when it is returned and check coverage and freshness before a research job, dashboard, export, or generated client uses the result. Order books, trades, OI, and L4 each retain their own route and coverage boundary.
Run One Route
How To Choose
1
Resolve the outcome
Start with
/v1/hyperliquid/hip4/outcomes or /v1/hyperliquid/hip4/questions. Keep the returned outcome identifier and side context with the later request.2
Keep probability units
Store
mark_price and mid_price as implied probabilities between 0 and 1. Do not join them to USD price fields without an explicit conversion model.3
Gate the window
Check the selected symbol with
/v1/symbols, the HIP-4 freshness route, and Data quality before the result feeds a decision.