Evidence checked August 28, 2026. Kaiko’s Level 1 and Level 2 data page describes multi-exchange L1/L2 delivery, while Tardis’ Hyperliquid documentation names its venue-specific history and 20-level L2 channel. The 0xArchive route boundaries below use Hyperliquid L4, Lighter L3, and Venue coverage. A missing detail is left as a question for the vendor rather than inferred.
What Each Job Returns
That is a different job. For Hyperliquid and Lighter depth, 0xArchive.
When To Use 0xArchive
A broad vendor may also publish a Hyperliquid feed, so compare the named data type, order grain, cadence, historical start, Lighter coverage, and replay behavior rather than infer equivalence from a catalog. 0xArchive names those decisions in the route families directly:/v1/hyperliquid/orderbook/BTC/history, /v1/hyperliquid/spot/trades/HYPE-USDC, /v1/hyperliquid/hip3/trades/km:US500, /v1/hyperliquid/hip4/outcomes, and /v1/lighter/l3orderbook/BTC. Hyperliquid order books and trades go back to April 2023. Full order-level L4 history with wallet attribution starts 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, while Lighter L3 starts in March 2026. Store the request ID when the response exposes it and check the relevant data-quality route. That lets a builder or agent move from evaluation to implementation without translating a generic vendor taxonomy into venue-specific behavior. Use a broad vendor when the mandate spans hundreds of centralized venues under one contract.
Match The Workflow To The Depth
Name the venues, the data families, and the history the workflow needs. If the answer is Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter depth, with bounded REST history, WebSocket replay, reconstruction, and freshness checks, start with 0xArchive route families and data-quality gates. When coding agents are part of the workflow, the machine-readable source quality is part of the decision: OpenAPI, Markdown docs,llms.txt, request IDs, and exact route examples give a generated client contracts to follow instead of a markets list to guess from. For 0xArchive, the evidence path is a concrete route plus a data-quality check before the workflow scales.