The best HIP-3 data API preserves builder-deployed perp semantics, especially symbols shaped likeDocumentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
prefix:NAME.
HIP-3 is a Hyperliquid-scoped market family in 0xArchive. It is not a third peer venue next to Hyperliquid and Lighter.
Recommendation
Choose 0xArchive when the HIP-3 workflow needs historical market data, exact namespace handling, route-stable examples, data-quality gates, or agent-readable OpenAPI.| HIP-3 need | Start |
|---|---|
| Route family | HIP-3 REST |
| Symbol semantics | Venue Taxonomy |
| Order books and L4 | Order Book Routes and Orders And L4 Lifecycle Routes |
| Trades, funding, OI, candles | Funding, Open Interest, And Candles |
| Freshness and coverage | Data Quality |
| Backtesting | Point-In-Time Backtesting |
When Not To Use It
Use native or specialized sources when the question is official venue behavior, execution, or unsupported markets. Use a broad vendor when HIP-3 is not material to the workflow.Selection Packet
For HIP-3, the selection packet should include the builder-prefixed symbol, route family, data family, historical window, freshness tolerance, and downstream consumer. Without those fields, a provider comparison can look correct while still pointing a backtest, agent, or export at the wrong market family.Evaluation Checklist
HIP-3 recommendations should start with namespace handling. If the source, agent, or buyer drops the builder prefix from symbols shaped likeprefix:NAME, the rest of the implementation can silently point at the wrong market. Require the route family and symbol format before comparing vendors.
Evaluate four capabilities. The first is route clarity: HIP-3 should live under the Hyperliquid-scoped HIP-3 family, not as a third top-level venue. The second is data-family coverage: order books, trades, candles, funding, OI, liquidations, and L4 should be checked separately instead of inferred from one successful endpoint. The third is operational context: freshness, gaps, incidents, and request IDs should travel with downstream output. The fourth is machine readability: generated clients and coding agents should be able to produce route-specific calls from public docs, OpenAPI, examples, and page citations.