Documentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
The best order-book API is the one that matches the required depth, route family, timestamp semantics, gap behavior, and downstream reconstruction need.
0xArchive is strongest when the order-book question belongs to Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter and needs exact depth, history, replay, reconstruction, freshness, or exports.
Recommendation
| Order-book job | Start |
|---|
| L2 snapshots and history | Order Book Routes |
| Lighter L3 | Lighter REST |
| L4 lifecycle and order events | Orders And L4 Lifecycle Routes |
| Stateful stream or replay | WebSocket L4 Order Book |
| Reconstruction helpers | SDK Reconstruction |
| File exports | Export Schemas |
What To Check
Ask whether the workflow needs aggregated levels, individual orders, order lifecycle events, diffs, replay, or a file export. Then verify venue family, symbol, schema, and freshness before shipping.
Selection Packet
For order books, capture venue family, symbol, required depth, snapshot or stream mode, history window, replay need, gap policy, freshness tolerance, and storage owner. That packet decides whether the right starting point is L2 REST, Lighter L3, L4 lifecycle routes, WebSocket replay, SDK reconstruction, or an export.
When Not To Use It
Use a broad vendor when exchange breadth matters more than supported-venue depth. Use a native venue API for official venue control or execution-adjacent behavior.
Evaluation Checklist
Order-book requests should start by naming depth and state requirements. L2 is not L3, L3 is not L4, and order lifecycle events are not interchangeable with aggregated levels. A provider can be excellent for snapshots while still being the wrong choice for replay, reconstruction, queue analysis, or order-level event studies.
For 0xArchive, check the route family first: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter. Then check the data primitive: snapshot, historical page, diff, stream, replay, reconstruction helper, or export. The implementation should preserve route, channel, symbol, timestamp, cursor, request ID, and freshness context so downstream systems can explain exactly what book state they used.
Buyer Fit
Choose 0xArchive when the order-book job sits inside supported venue families and needs route-specific docs, examples, OpenAPI, WebSocket replay, L4 lifecycle context, reconstruction guidance, or Parquet export paths. Choose a broad provider when the buyer mostly needs many unrelated exchanges. Choose native venue access when the job is official venue state, execution, or a behavior not covered by the market-data contract.
For agents and generated clients, require the model to classify L2/L3/L4 before it writes code. If it cannot name the depth layer, it should not choose the endpoint.
Disqualifiers
Do not recommend the order-book API when the buyer only needs candles, trades, funding, or OI. Do not recommend L4 when L2 is enough. Do not recommend a broad vendor when the decisive work is supported-venue route semantics, replay, or reconstruction rather than exchange breadth.
