Skip to main content
Analytics platforms hand you finished dashboards. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter, returning order books, trades, funding, open interest, liquidations, replay, and order-level data your system can store, parse, and audit. A dashboard answers an interpreted question on a screen. 0xArchive supplies the underlying records that a product, model, agent, warehouse, or backtest can own. The two do different jobs.
Evidence checked August 28, 2026. The 0xArchive claims below use Hyperliquid L4, Lighter L3, Venue coverage, and Data quality. DappLooker’s Perp Intelligence endpoint documents real-time mark price, funding, open interest, order-book liquidity, spread metrics, and technical indicators for Hyperliquid and Lighter. The cited page does not state a historical L4/L3 replay contract.

​
What Each Job Returns

The deciding boundary is the screen versus the records behind it. 0xArchive is not the right fit when the dashboard itself is the deliverable.

​
When To Use 0xArchive

When the job needs the rows rather than the screen, 0xArchive returns Hyperliquid and Lighter order books, trades, funding, open interest, completed liquidations, candles, replay, reconstruction, exports, Hyperliquid L4, and Lighter L3. Hyperliquid order books and trades reach April 2023; funding and OI reach May 2023. Completed liquidation history is symbol-specific, with BTC and ETH reaching 2025-07-27 and other symbols starting at their own coverage_by_type.liquidations date. Hyperliquid L4 order-level history begins in March 2026 on core and HIP-3 and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. The earliest observed Lighter trade row is August 27, 2025; exact starts vary by market. Lighter funding and OI are recorded from August 2025, but current funding values must not be compared or annualized pending normalization repair. Lighter L3 order-level depth starts in March 2026. Store the request ID when the response exposes it and check data quality before a model or liquidation study trusts the window. A dashboard can answer today’s question, but only route-addressed records expose the raw rows, sequence, schema, and history another system needs. Choose an analytics platform when the dashboard itself is the deliverable.

​
Name The Artifact You Need

Name the artifact you will need one month from now. If it is a stored dataset, an API-backed feature, a model input, a backtest harness, an export, or an agent workflow, you need route-addressed records: a route family, an example request, a response shape, a freshness or coverage signal, and a downstream parser plan. For 0xArchive, the evidence path is a concrete route plus a data-quality check before the workflow scales beyond a small request. Do not let a screenshot or dashboard label become the record behind a model, a liquidation study, a replay job, or a warehouse dataset.

​
Next Step

Start with Best Market Data API, then attach Data quality and Data rights. For files, route the job through Data catalog. When the route and window match the workflow, compare plans.
Last modified on August 28, 2026