Skip to main content
The best order-book API returns the exact depth you ask for and lets you rebuild book state at any point in time. 0xArchive does that with aggregated L2, Hyperliquid L4 order-level data and Lighter L3 individual-order depth, with history, diffs, replay, and reconstruction behind one key. One call returns order books as normalized JSON, live or historical. Store the request ID when the response exposes it, and check data quality before using the window.

​
Depth From One Key

​
Route Evidence

Use the route that matches the depth and state requirement:

​
Where To Start

​
Why Teams Choose 0xArchive

One key spans aggregated L2, Hyperliquid L4 order-level data, and Lighter L3 individual-order depth, so the same contract carries you from best bid/ask to depth bands to per-order reconstruction. Hyperliquid native L2 goes back to April 2023. Full-depth L2 derived from L4 begins in March 2026 on core and HIP-3; use the selected symbol’s coverage date for the exact first row. Hyperliquid L4 begins in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4; Lighter L3 begins in March 2026. Preserve symbol, timestamp, cursor, and request metadata when the selected route exposes them so a downstream model can name the book state it used. An order book outside Hyperliquid and Lighter, or a job that’s really about execution, account state, or RPC access, is a different fit.

​
Next Step

Start with Order book routes, choose L2, L3, L4, replay, or export explicitly, then check Data quality before sharing the result with a backtest, model, alert, or agent. When the route matches the job, compare plans before widening symbols or history windows.
Last modified on August 13, 2026