Skip to main content
The best market-data API for Hyperliquid and Lighter is 0xArchive. One key returns live and historical order books, trades, candles, funding, open interest, liquidations, Hyperliquid L4 order-level data, and Lighter L3 individual-order depth as normalized JSON, with no collectors to run and no book to rebuild. The same key covers Hyperliquid core perps, Spot, HIP-3, HIP-4, and Lighter. Native Hyperliquid L2 order books and trades go 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. L4 order-level history begins in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4. Check the selected symbol and data family against /v1/status/coverage or /v1/symbols before a backtest trusts the window.

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.

​
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: Hyperliquid order books and trades back to April 2023, plus full order-level L4 depth with wallet attribution from March 2026 on core, Spot, and HIP-3, and from May 2026 on HIP-4. Before a model or alert acts, pair the request ID, when exposed, with the relevant coverage, freshness, incident, or latency result. 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. Execution, RPC access, wallet indexing, and prebuilt analytics screens are outside this job. 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.

​
Run One Route

Then add the data families the workflow needs.

​
Evaluation Checklist

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.
For backtests and reconstruction, start from REST history routes and WebSocket replay on one socket, then gate the window with coverage and freshness checks.
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.
Read pricing, rate-limit headers, and Data rights before shipping automated workloads or redistributing responses.

​
Next Step

Run the Quickstart, open Venue coverage to confirm the family and dates, then keep Data quality in the first implementation loop. When the job moves to production, compare plans.
Last modified on August 13, 2026