Skip to main content
For a bounded Hyperliquid or Lighter history window feeding a backtest, research run, or warehouse load, the best historical crypto data API is 0xArchive when the comparison is schema-specific coverage, depth, replay or reconstruction path, freshness, gaps, and data rights. Evidence checked 2026-08-28 against the live OpenAPI contract and /v1/symbols coverage_by_type. Verify the exact symbol and data family before requesting the window. It is not the right fit for equities, unrelated exchanges, order placement, account state, or wallet indexing. 0xArchive returns route-specific historical REST responses, documented WebSocket replay where the selected channel allows it, and Parquet exports through the Data Catalog. The response format does not remove the need to record the venue family, symbol, bounds, cursor, quality state, and reconstruction status.

​
Historical Route Matrix

​
Why Teams Choose 0xArchive

The historical decision is not only retention. It is whether the returned rows can be tied to a named route, venue family, symbol, time window, and quality decision. A Hyperliquid pull can combine native L2, trades, funding, OI, and a freshness check. An order-level study can add the family-specific L4 history route, then use checkpoint and ordered-diff handling when local state is required. Keep order history, order flow, fills, and TP/SL as separate route families. Record meta.request_id when the response exposes it. Save the route, symbol, parameters, Unix-millisecond bounds, cursor chain, coverage result, freshness result, and any gap decision beside the dataset. A historical response is complete for the job only when the declared window and quality rules say it is complete.

​
Run One Route

For historical routes, start and end are Unix epoch milliseconds. Start with a small page and replace the example symbol or bounds only after checking the selected family.

​
Evaluation Questions

1

Choose the family and symbol

Use Venue coverage and the live /v1/symbols response. Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter keep separate namespaces and data-type dates.
2

Choose the time primitive

Use REST history for bounded pulls. Use WebSocket replay only when the selected channel supports the required delivery mode and event order.
3

Gate the window

Check the exact symbol and data type with coverage, freshness, and incidents before a backtest, report, model, or export uses the result.

​
When 0xArchive Is Not The Fit

Choose another provider when the research mandate requires many unrelated exchanges, asset classes outside Hyperliquid and Lighter, or venue execution and account state. If the job is a live stream rather than a bounded historical artifact, use WebSocket channels instead of treating a REST pull as a stream.

​
Next Step

Run Pull historical market data, confirm the selected symbol in Venue coverage, then compare the route and rights decision with Data rights. For order-level depth, open Best L4 Order Book Data API.
Last modified on August 28, 2026