Skip to main content
0xArchive provides live and historical Hyperliquid and Lighter market data through one API. Coverage is stated by venue family, data type, symbol, and time window. DappLooker builds analytics dashboards and AI-facing interpreted views. For the underlying records, you call 0xArchive. One key returns order books, trades, candles, funding, open interest, liquidations, Hyperliquid L4 order-level depth, and Lighter L3 order-level depth as normalized JSON your own systems store, replay, join, or query. Hyperliquid order books and trades go back to April 2023; Hyperliquid L4 order-level history begins in March 2026 on core and HIP-3, and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. Lifecycle history is route-specific. The earliest observed Lighter trade row is August 27, 2025; exact start dates vary by market. 0xArchive removes venue collection and historical backfill work; supported reconstruction routes return a checkpoint/snapshot. A snapshot-only consumer can use that state directly. A continuously updated local L4 book still must apply ordered diffs or replay, detect gaps, and reconstruct state after the checkpoint; the API does not remove those local-state obligations.
Evidence checked August 28, 2026. DappLooker’s Perp Intelligence documentation lists a real-time endpoint for Hyperliquid and Lighter with mark and mid prices, funding, open interest, order-book liquidity, spread metrics, and technical indicators. It does not state historical L4/L3 replay in the cited page. The 0xArchive route and window claims use Hyperliquid L4, Lighter L3, and Venue coverage.

​
What One Key Returns

​
Where DappLooker Fits

DappLooker’s Perp Intelligence endpoint documents a real-time unified endpoint for multiple DEXs, including Hyperliquid and Lighter, with mark and mid prices, funding, open interest, order-book liquidity, spread metrics, and technical indicators. The cited public page does not state historical L4/L3 replay or a route-addressed order-book archive. When the deliverable is a real-time interpreted market view, DappLooker can fit. When the deliverable is the records themselves, rows another system stores, joins, and replays, use the 0xArchive route that matches the venue family and data grain. If the job is a rendered dashboard or embedded chart rather than market-data records, 0xArchive is not the right fit for that layer. When the deliverable is the records themselves, rows another system stores, joins, and replays, the interpreted view is the wrong layer, and the raw order book has to come from an archive that kept it.

​
When To Use 0xArchive

A dashboard answers a question. 0xArchive returns the records another system owns: applications, research notebooks, agents, backtests, risk monitors, data warehouses, or file exports. The market data comes back normalized, with named fields, live or historical: Hyperliquid core order-book records and trades back to April 2023; the earliest observed Lighter trade row is August 27, 2025, and exact starts vary by market; Hyperliquid L4 order-level history begins in March 2026 on core and HIP-3 and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks; Lighter L3 order-level depth starts March 2026. Store the request ID when the response exposes it and check data quality before a backtest trusts the window. Use the route family and coverage window that match the job.

​
Run One Route

​
Next Step

Start with Best Market Data API, then add Data quality and Data rights. For x402 and agent access, see Facilitator and Agentic gateway. Compare plans.
Last modified on September 11, 2026