Skip to main content
Analytics platforms hand you finished dashboards. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter, returning every order, trade, and fill as records your system can store, parse, replay, 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.

​
What Each Job Returns

NeedAnalytics platform0xArchive
Prebuilt dashboards and screensRenders finished charts and viewsA different data object
Interpreted metrics and ranked tablesComputes and displays the metric for youA different data object
No-code visual explorationPoint-and-click interface over a fixed datasetA different data object
Hyperliquid order books and trades, live and historicalA finished view, not the rows20-level L2 snapshots about every 1.2 seconds and trades since April 2023, 24.6B+ records, 176 symbols
Funding, open interest, liquidationsA finished view, not the rowsFunding and OI since May 2023; liquidations since December 2025
Order-level (L4) depth and lifecycleA finished view, not the rowsEvery order add, fill, cancel, and TP/SL with wallet attribution since March 2026 (Hyperliquid families)
Lighter order books, trades, L3A finished view, not the rowsTrades since August 2025; L2 tick since January 2026; L3 since March 2026
Product-owned data pipelineA different data objectRoute-stable JSON for apps, models, and agents
Backtests and replayA different data objectREST history, WebSocket replay, and reconstruction with request IDs
Warehouse filesA different data objectData Catalog exports tied to supported venues
That is a different job. For Hyperliquid and Lighter market data, 0xArchive.

​
When To Use 0xArchive

When the job needs the rows, not the screen, 0xArchive returns supported Hyperliquid and Lighter records: order books, trades, funding, OI, liquidations, candles, L3/L4, replay, reconstruction, and exports. Hyperliquid order books and trades go back to April 2023 across 176 symbols and more than 24 billion records, funding and OI since May 2023, liquidations since December 2025, and full order-level (L4) depth with wallet attribution since March 2026; Lighter trades land from August 2025 and L3 from March 2026. Every response carries a request ID and a data-quality path you can check 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. 0xArchive is not the right fit when the deliverable is the dashboard itself; an analytics platform ships that screen faster than an API will. Live or historical, every order, trade, and fill, one API.

​
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 July 4, 2026