Evidence checked August 28, 2026. Tardis’ Hyperliquid documentation, Lighter documentation, CSV documentation, and billing FAQ are the first-party sources for the provider claims. The 0xArchive route and window claims use Hyperliquid L4, Lighter L3, and Venue coverage.
What One Key Returns
Where Tardis Fits
Tardis documents a broad exchange catalog with tick-by-tick order-book snapshots and updates, trades, open interest, funding rates, liquidations, and options data delivered through CSV downloads, an HTTP API, and Tardis Machine. Its Hyperliquid page lists a 20-levell2Book channel, and its Lighter page documents Lighter history without stating an order-book depth. Its billing documentation distinguishes CSV-only from API and Machine access and ties historical access to subscription terms. Choose Tardis when options data or one pipeline across many centralized venues is the deciding workload. Choose 0xArchive when order-level depth on Hyperliquid and Lighter is the deciding workload. If the required venue is outside Hyperliquid and Lighter, 0xArchive is not the right fit for that breadth requirement.
On the two venues this API covers, the decision flips to depth: Tardis’ cited Hyperliquid page describes tick-level L2 book data, while 0xArchive carries the full order-level (L4) stream with wallet attribution on Hyperliquid and native L3 on Lighter.
When To Use 0xArchive
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. The market data comes back normalized, with named fields, live or historical. Hyperliquid order-book records and trades reach April 2023. L4 history with wallet attribution begins in March 2026 on core and HIP-3 and in May 2026 on HIP-4. For Spot, verify order-event and reconstructable-checkpoint coverage separately. Lighter native L2 tick begins in January 2026, and L3 order-level depth begins in March 2026. Store the request ID when the response exposes it and check data quality before a backtest trusts the window. Standard replay runs on the same WebSocket as the live stream at 10x to 300x by plan and up to 500x on Enterprise. Core L4 replay instead uses checkpoint-anchored bulk delivery and ignoresspeed; Spot channels and HIP-3 and HIP-4 L4 are real-time-only. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; inspect the family-specific route and selected symbol coverage before relying on it.