/v1/hyperliquid/hip3/* routes. HIP-3 symbols are case-sensitive, so km:US500 is not interchangeable with KM:US500 or an unprefixed US500.
Observed HIP-3 trade coverage across current symbol rows begins October 13, 2025, with exact starts varying by market. Native L2, funding, and open interest begin February 16, 2026; L4 coverage begins March 10, 2026 where the selected symbol exposes the relevant key. Funding rows are captured at roughly 10-second resolution. Use the selected symbol’s coverage and freshness metadata for the exact window rather than inferring a venue-wide history.
HIP-3 REST
Namespace, examples, and route families.
Venue coverage
Symbol and route selection rules.
Route Scope
The current contract keeps builder-perp routes under/v1/hyperliquid/hip3/*. It includes order books, trades, candles, funding, open interest, CVD, liquidations, liquidation levels, oracle context, and order-history routes. A listed route does not establish non-empty coverage for every symbol; use the selected operation’s coverage and freshness checks before relying on its window. Liquidation routes can return valid empty pages when no rows match the symbol and window.
Implementation Pattern
For a builder-perp backtest, monitor, report, or generated client, start with one symbol such askm:US500, one route, and a small window. Check coverage and freshness before using the output in a backtest, report, alert, or model. Keep the prefix in storage and logs. If a coding agent writes the client, give it OpenAPI plus HIP-3 REST so it does not strip or recase the prefix, skip HIP-3 oracle routes, or choose a core route.
Next Step
Open HIP-3 REST, then use Venue coverage and Data quality before widening to more markets.Symbol Boundary
If the request is onlyUS500 without a prefix, identify the source venue before generating code. If it includes a builder prefix, keep it intact through URL construction, storage, dashboards, exports, and model features.