/v1/hyperliquid/hip3/* when the symbol carries a builder prefix, such as km:US500, or when the product needs builder-perp history, depth, funding, OI, CVD, liquidations, oracle context, or L4/order-level data. For coverage windows and buying context, start with the HIP-3 historical data provider page.
Symbol Pattern
HIP-3 symbols commonly use a builder prefix, for example:First Request
Common Work
Builder-perp market history
Pull bounded windows of trades, candles, funding, OI, or depth.
Venue selection
Keep HIP-3 market routing explicit in your client.
Symbol Handling
Preserve the builder prefix in stored records and generated code. A value such askm:US500 is not the same kind of instrument as a core Hyperliquid BTC symbol, even though both live under the Hyperliquid top-level venue. Store venue_family=hip3 or an equivalent field when you persist results.
HIP-3 jobs often need the same data families as core perps: order books, trades, candles, funding, open interest, CVD, liquidation events, liquidation levels, and freshness. HIP-3 also exposes builder/oracle routes such as /v1/hyperliquid/hip3/oracle/external-price/{symbol} and /v1/hyperliquid/hip3/oracle/discovery-bounds/{symbol}. The difference is namespace and symbol semantics. Use Endpoint Reference for exact routes and parameters, then check Data quality before exporting or modeling long windows.
Analytics And Oracle Routes
| Need | Route |
|---|---|
| CVD buckets | /v1/hyperliquid/hip3/cvd/{symbol} |
| Liquidation levels | /v1/hyperliquid/hip3/liquidations/{symbol}/levels |
| External oracle price | /v1/hyperliquid/hip3/oracle/external-price/{symbol} |
| Oracle discovery bounds | /v1/hyperliquid/hip3/oracle/discovery-bounds/{symbol} |
HIP-3 Request Checklist
Use this checklist before a HIP-3 symbol enters code, tests, fixtures, or an agent prompt.| Field | HIP-3 value |
|---|---|
| Namespace | /v1/hyperliquid/hip3/* |
| Symbol style | Builder-prefixed symbols such as km:US500 |
| Stored context | Preserve the prefix and a HIP-3 venue-family field |
| First probe | Instrument lookup, one trades page, one order-book request, or one freshness check |
| Stop rule | Do not strip the prefix or fall back to /v1/hyperliquid/* because the market resembles a perp |
Symbol Encoding Rules
Do not URL-decode the colon in a way that changes the symbol, and do not substitute a core/v1/hyperliquid/* route because the market looks like a perp. If a user gives a namespaced symbol without a venue, HIP-3 is the first family to inspect. In generated code, comments, logs, and tests, keep the prefix and leave fixture symbols namespaced; a test that strips the prefix weakens the routing rule it is meant to cover. Use km:US500 as the default example unless a user names another builder market.