/v1/symbols coverage_by_type. Verify the exact route and symbol before using the book. It is not the right fit for an order book outside Hyperliquid and Lighter or for execution, account state, or RPC access.
L2 is aggregated price-level depth. L3 is individual Lighter resting orders. L4 is Hyperliquid resting-order state. Order history, order flow, fills, and TP/SL are separate objects.
Depth Decision Matrix
Route Evidence
Why Teams Choose 0xArchive
The route family makes the depth decision explicit. Use L2 when price levels answer the question. Use Lighter L3 or Hyperliquid L4 when individual resting orders matter. Use diffs, checkpoints, and replay when the application must maintain state over a sequence rather than consume one snapshot. A local reconstruction must apply the selected checkpoint and ordered updates, record sequence and gap events, and rebuild when the channel says the state is no longer safe. Store the route, family, symbol, timestamp, cursor, quality result, andmeta.request_id when exposed. Do not treat an L4 book as order lifecycle data.
Selection Checklist
1
Name the depth layer
Decide L2, L3, or L4 before choosing a vendor. Lighter order-level work uses L3; Hyperliquid order-level work uses L4.
2
Choose snapshot or stateful delivery
Use REST history for bounded snapshots. Use diffs, WebSocket replay, or SDK reconstruction when the local book must evolve across events.
3
Check the selected window
Read the exact symbol’s
coverage_by_type, freshness, and incident state before a model, alert, export, or agent call trusts the book.