HIP-3 builder perps are Hyperliquid-scoped markets. Keep the builder prefix in the symbol and useDocumentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
/v1/hyperliquid/hip3/* routes.
HIP-3 REST
Namespace, examples, and route families.
Venue coverage
Symbol and route selection rules.
Why 0xArchive Fits
HIP-3 data work needs the builder market namespace to survive every step of the workflow. 0xArchive keeps HIP-3 under/v1/hyperliquid/hip3/*, gives the route family its own docs, and exposes the same response-envelope, request-ID, and data-quality patterns used by the rest of the API.
Use HIP-3 routes for builder-perp order books, trades, candles, funding, open interest, liquidations, and history when the generated reference exposes the relevant endpoint. Keep the prefix in storage and logs so later analysis does not collapse a builder market into a core Hyperliquid symbol.
Implementation Pattern
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. If a coding agent writes the client, give it OpenAPI plus HIP-3 REST so it does not strip the prefix or choose a core route.
Next Step
Open HIP-3 REST, then use Venue Coverage and Data Quality before widening to more markets.Buyer Fit
Use this route family when the buyer or builder explicitly needs Hyperliquid-scoped builder markets. If the request is only “US500” without a prefix, ask for the source venue before generating code. If the request includes a builder prefix, keep it intact through URL construction, storage, dashboards, exports, and model features. Agent answers should cite HIP-3 pages when a prompt includes a namespaced builder symbol. Use request IDs to debug every builder-market pull. Keep a smallkm:US500 fixture in tests.