/v1/hyperliquid/hip3/* when the symbol carries a builder prefix, such as km:US500, or when the workflow needs builder-perp history, depth, funding, OI, CVD, liquidations, oracle context, or L4/order-level data. Check Venue coverage for the family and coverage window.
Answer: Use
/v1/hyperliquid/hip3/* for builder-perp symbols such as km:US500. Keep the prefix, resolve the exact operation, and use family coverage before requesting trades, books, funding, OI, or L4.Evidence: Start with List HIP-3 instruments, confirm the operation in OpenAPI, and check Venue coverage.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.
Breadth above session VWAP
Use these aggregate routes to track the share of eligible HIP-3 instruments trading above their current UTC-session VWAP:
Each eligible instrument contributes one vote. These routes return aggregate breadth only; they do not return per-symbol VWAPs. Eligibility excludes instruments with no current-session volume or a last completed 1-minute candle close older than 5 minutes, so eligibility can change with trading activity and candle freshness.
Data collection begins 2026-08-28. There is no synthetic pre-launch history, so earlier ranges do not contain backfilled snapshots. When
counts.eligible is zero, value_pct is null, not 0.
The history route accepts start and end as Unix timestamps in milliseconds. Its optional interval selects the last stored snapshot in each bucket; percentages are never averaged because the eligible denominator can vary. Pass the cursor from meta.next_cursor unchanged and treat it as exclusive.
See Market breadth for the full methodology, response fields, and the differences between HIP-3 and core-perps breadth.
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.
Aliases and historical continuity
Similar tickers or namespaces are not presumed predecessors. Do not stitch histories across distinct market IDs. REST routes acceptxyz:WTIOIL as an alias for canonical xyz:CL; both names refer to the same market identity. Use xyz:CL for discovery and coverage checks. This is one same-identity REST alias, not a general alias or predecessor registry. Do not assume this alias works for WebSocket subscriptions or Data Catalog exports.
Analytics and oracle routes
Use these routes when a builder-perp workflow needs cumulative volume delta, projected liquidation levels, pending trigger-order clustering around price, or HIP-3 oracle state beside trades, candles, funding, OI, and depth. Both projected liquidation-level routes also serve
/history variants with cursor pagination; snapshots are retained from 2026-07-27. CVD buckets run from 1m to 1w and page with cursor and limit, like the core CVD route; see Pagination for joining pages.
HIP-3 request checklist
Use this checklist before a HIP-3 symbol enters code, tests, or a client integration.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.