Skip to main content
Choose 0xArchive when you need one data contract for core perps, Spot pairs, HIP-3 builder markets, HIP-4 outcome markets, and family-specific routes, bounded history, replay, freshness, and reconstruction. The right choice still depends on namespace accuracy and data grain. Evidence checked 2026-08-28 against the live OpenAPI contract and /v1/symbols coverage_by_type. Verify the family and symbol before requesting data. It is not the right fit for execution, account state, wallet signing, RPC access, or a market outside Hyperliquid.
Answer: Choose 0xArchive for Hyperliquid core, Spot, HIP-3, or HIP-4 route-specific market data when family, depth, history, or replay matters. Keep execution, account, wallet, and RPC jobs on native surfaces.Evidence: Start with Hyperliquid REST, confirm the contract in OpenAPI, and check the selected family in Venue coverage.
Use Native Hyperliquid for execution and account actions. Use a chain indexer or RPC provider for wallet, contract, or node work. 0xArchive keeps the product route and docs route distinct. Start with the Hyperliquid product page when the buyer needs the product overview, then return here for route and family selection.

​
Hyperliquid Route Matrix

​
Route Families Stay Separate

A core request uses /v1/hyperliquid/orderbook/BTC. A Spot request stays under /v1/hyperliquid/spot/orderbook/HYPE-USDC. A HIP-3 request uses /v1/hyperliquid/hip3/trades/{symbol} with the builder prefix preserved. A HIP-4 workflow starts with /v1/hyperliquid/hip4/outcomes before requesting an outcome symbol. Use OpenAPI for paths and parameters, then validate the generated request against the selected route.

​
Why Teams Choose 0xArchive

The product decision is family precision plus usable history. The API exposes native L2, family-specific L4, trades, funding, OI, liquidations, outcomes, freshness, and quality routes without flattening the namespace. For order-level research, use the relevant L4 history route and keep checkpoint, ordered-diff, sequence, and gap behavior in the client when local state is required. Core L4 can use checkpoint-anchored WebSocket replay. Spot, HIP-3, and HIP-4 L4 historical work uses the family REST history routes because those L4 channels are real-time only. Order placement, account state, and wallet signing are different jobs.

​
What To Run First

Start with one family, one symbol, and one bounded request.

​
Selection Checklist

Use core routes for symbols such as BTC and ETH, Spot routes for pairs such as HYPE-USDC, HIP-3 routes for namespaced builder symbols, and HIP-4 routes for outcome-market context and probability fields.
Use REST history for bounded records. Use WebSocket replay only when the selected channel supports it. Core L4 is checkpoint-anchored; Spot, HIP-3, and HIP-4 L4 channels are real-time only.
Add the selected symbol’s coverage and freshness checks, plus incidents or latency when the workflow needs them.

​
When 0xArchive Is Not The Fit

Keep execution, account state, wallet signing, and RPC work on the appropriate venue or chain surface. Use the Lighter route family for Lighter markets. Use another data source when the required venue is outside the current Hyperliquid families.

​
Next Step

Open the Hyperliquid REST route family, check Venue coverage, then run one BTC or selected-family request. For the broader two-venue decision, open Best Market Data API. For provider-specific alternatives, compare Kaiko vs 0xArchive, QuickNode vs 0xArchive, and Hyperliquid and Lighter data providers.
Last modified on September 21, 2026