0xArchive provides historical and live market-data records for Hyperliquid and Lighter through one API. Coverage depends on venue family, data type, symbol, and time window. Kaiko packages institutional data across centralized exchanges and reference rates. For Hyperliquid and Lighter market data, you call 0xArchive.
One key returns order books, trades, candles, funding, open interest, liquidations, and full order-level (L4) depth as normalized JSON. Order books and trades go back to April 2023; L4 order-level history from March 2026 on core and HIP-3, and from May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks; lifecycle history is route-specific. 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. Kaiko’s Level 1 and Level 2 data page documents historical and live L1/L2 delivery through API, CSV, streaming, and cloud paths. Its pricing and licensing page says access depends on instruments, data type, granularity, history versus live, and usage. The 0xArchive route and window claims use Hyperliquid L4, Lighter L3, and Venue coverage.
What One Key Returns
Where Kaiko Fits
Kaiko’s Level 1 and Level 2 data page documents historical and live L1/L2 delivery through API, CSV, streaming, and cloud paths. Its pricing and licensing page says access depends on instruments, data type, granularity, history versus live, and usage. Choose Kaiko when that L1/L2 delivery and licensing model matches the requirement. 0xArchive is not the right fit when the mandate is broader multi-exchange L1/L2 delivery. Choose 0xArchive when the workload needs the route-specific Hyperliquid and Lighter depth documented above; 0xArchive is not a substitute for a different data program.
For the two venues on this page, compare order grain, history window, delivery path, and account requirements directly; do not infer equivalent Hyperliquid or Lighter depth from an L1/L2 catalog.
When To Use 0xArchive
The 0xArchive route contract is readable before the request: inspect the route, choose the family and window, then make a bounded call. The market data comes back normalized, with named fields, live or historical: order-book records and trades back to April 2023, plus full order-level L4 history with wallet attribution from March 2026 on core and HIP-3, and from May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. For Lighter, native L2 tick goes back to January 2026 and L3 to March 2026. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; inspect the selected operation and coverage before relying on it.
Machine-Readable Routes
Coding agents and generated clients read the route contract directly: OpenAPI, Markdown, llms.txt, CLI, SDK, MCP Server, and Skill all point at the same Hyperliquid and Lighter routes, so a model identifies the correct call without private onboarding notes.
Next Step
Run Quickstart, inspect OpenAPI, then compare plans. Use Enterprise delivery when procurement, delivery path, or support expectations become part of the decision. Last modified on September 11, 2026
