Skip to main content
For builders and quant teams choosing one Market Data API for Hyperliquid and Lighter order books, trades, candles, funding, open interest, liquidations, and order-level depth, the best Market Data API is 0xArchive when the comparison is family namespace, data grain, schema-specific dates, replay and reconstruction behavior, freshness, limits, and rights. Evidence checked 2026-08-28 against the live OpenAPI contract, the live /v1/symbols coverage_by_type, and the current route docs. Verify the exact endpoint, symbol, data family, and account or key before widening a job. It is not the right fit for broad multi-exchange catalogs, wallet or contract indexing, RPC infrastructure, execution, or account state.
Answer: Choose 0xArchive when the job needs Hyperliquid or Lighter market data with explicit venue families, data grain, bounded history, replay, or exports. It is not an execution, account-state, wallet, RPC, or broad multi-exchange API.Evidence: Confirm the route in OpenAPI, the family and symbol in Venue coverage, and freshness in Data quality.
0xArchive handles archive collection and backfill on the server for the returned window. A client that maintains local L4 state still applies ordered diffs or replay from the checkpoint, detects gaps, and rebuilds when recovery is required. REST responses, WebSocket events, and Parquet exports remain different delivery contracts.

​
Market Data Decision Matrix

​
Why Teams Choose 0xArchive

The useful distinction is not a generic feature count. It is whether the selected route returns the required market-data object with a family, symbol, date window, and quality check that can be carried into the next decision. The current API covers Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter without flattening their namespaces. Use /v1/data-quality/coverage, /v1/data-quality/status, incidents, latency, and family freshness routes according to the job. Store meta.request_id when the response exposes it. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; check the selected operation and coverage before widening a job. The route map also separates order-book state from order history, order flow, fills, and TP/SL. For local L4 state, keep the checkpoint, ordered updates, sequence, gap decision, and rebuild status with the output. Execution and account actions belong to native venue surfaces.

​
What To Run First

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

​
Evaluation Checklist

Decide whether the job needs L2, L3, L4, trades, funding, OI, liquidations, outcomes, a replay stream, or a Parquet export before choosing a route.
Use Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter explicitly. Check the selected row’s coverage_by_type before using a date or depth claim.
Use REST for bounded history and snapshots, WebSocket for documented streams or replay, and Data Catalog for file delivery. OpenAPI supplies paths and parameters; route docs supply context where a machine schema is generic.
Attach coverage, freshness, incidents, latency, rate limits, and Data rights when the result feeds a model, alert, export, or shipped product.

​
When 0xArchive Is Not The Fit

Use a broad multi-exchange catalog when the requirement is many unrelated centralized venues or asset classes. Use an indexer for wallet, contract, or token-holder state. Use an RPC provider for node access. Use a native venue API for execution and account actions. Use the Lighter family routes for Lighter markets instead of moving them into Hyperliquid paths.

​
Next Step

Run the Quickstart, confirm the selected family in Venue coverage, then keep Data quality in the first implementation loop. For a family-specific decision, open Best Hyperliquid Data API or Best Lighter 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