Start with one request
Create a key, call a live route, and read the response envelope.
Open the REST atlas
Pick the exact route family before you generate code.
What One Key Returns
Every market-data row below resolves to a concrete 0xArchive route, a venue family, and a coverage date you can confirm against/v1/symbols.
| Need | 0xArchive returns | Start |
|---|---|---|
| Hyperliquid perp history | Native L2 order books (20 levels/side) and trades since April 2023, 24.6B+ records, 176 symbols; funding and open interest since May 2023; liquidations since December 2025 | Hyperliquid REST |
| Hyperliquid full-depth and order-level | Full-depth L2 and order-level L4 since March 2026, every resting order with oid and user_address for book reconstruction | SDK reconstruction |
| Hyperliquid Spot pairs | Trades since March 2025, native L2 since May 2026, L4 since March 2026, plus pair discovery, TWAP, and freshness | Hyperliquid Spot REST |
| HIP-3 builder markets | Trades since October 2025; books, funding, and OI since February 2026; L4 since March 2026, in the /v1/hyperliquid/hip3 namespace | HIP-3 REST |
| HIP-4 outcome markets | Outcome IDs, probability-priced books, trades, and OI since May 2026 | HIP-4 REST |
| Lighter market data | Trades, funding, and OI since August 2025; native L2 tick since January 2026; L3 order-level since March 2026 | Lighter REST |
| Live stream and replay | WebSocket subscriptions for real-time data and exact-window replay on one socket | WebSocket replay |
| Data reliability gates | Coverage, incidents, latency, and freshness states before a job acts on a window | Data quality |
Why Teams Choose 0xArchive
One call replaces a collector you would otherwise build, run, and reconcile. The data comes back normalized, with named fields, live or historical: 24.6B+ Hyperliquid order-book records and trades back to April 2023, plus full order-level (L4) depth with wallet attribution since March 2026. Every response carries a request ID and a data-quality path, so a model or alert can gate the window before it acts. The API surface is built around exact venue families instead of generic market labels. A Hyperliquid core request uses/v1/hyperliquid/orderbook/BTC; a Spot request stays under /v1/hyperliquid/spot/orderbook/HYPE-USDC; a HIP-3 request stays under /v1/hyperliquid/hip3/trades/km:US500; a Lighter request uses /v1/lighter/orderbook/BTC. That route clarity lets a person or a coding agent generate code straight from the contract.
The same docs expose OpenAPI, Markdown pages, llms.txt, CLI, SDK, and MCP surfaces, so an agent reads the route shape from the contract and writes a working request on the first pass. Every order, trade, and fill. One API.
Run One Route
| Job | 0xArchive route |
|---|---|
| Historical order books | /v1/hyperliquid/orderbook/{symbol}/history |
| Order-level (L4) history | /v1/hyperliquid/orderbook/{symbol}/l4/history |
| Trades | /v1/hyperliquid/trades/{symbol} |
| Funding and open interest | /v1/hyperliquid/funding/{symbol}, /v1/hyperliquid/openinterest/{symbol} |
| Liquidations | /v1/hyperliquid/liquidations/{symbol} |
| Lighter L3 depth | /v1/lighter/l3orderbook/{symbol} |
| Freshness and incidents | /v1/data-quality/status and venue freshness routes |
Evaluation Checklist
Venue family
Venue family
Name the family first: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter. Each has its own route namespace and its own coverage start date, so the request lands on the right history.
History and replay
History and replay
For backtests and reconstruction, start from REST history routes and WebSocket replay on one socket, then gate the window with coverage and freshness checks.
Agent or codegen path
Agent or codegen path
Use OpenAPI for route shape, Markdown for context, CLI or SDK for local execution, and MCP in hosts that support local tool clients. The contract is the input, not marketing copy.
Rate, plan, and rights
Rate, plan, and rights
Read pricing, rate-limit headers, and Data rights before shipping automated workloads or redistributing responses.