> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tardis Vs 0xArchive

> Tardis covers historical Hyperliquid and Lighter datasets plus broader exchanges. 0xArchive provides Hyperliquid and Lighter market-data routes.

Tardis documents historical Hyperliquid and Lighter datasets alongside broader multi-exchange coverage. Compare the providers by venue, data family, depth, delivery path, and history window. 0xArchive provides Hyperliquid L4 order-level data and Lighter L3 individual-order depth; the coverage routes state the family, symbol, and window boundaries.

One key returns Hyperliquid order books, trades, candles, funding, open interest, liquidations, and Hyperliquid L4 order-level depth, plus Lighter order books, trades, funding, open interest, and L3 order-level depth as normalized JSON. 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. 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.** Tardis' [Hyperliquid documentation](https://docs.tardis.dev/historical-data-details/hyperliquid), [Lighter documentation](https://docs.tardis.dev/historical-data-details/lighter), [CSV documentation](https://docs.tardis.dev/downloadable-csv-files/api), and [billing FAQ](https://docs.tardis.dev/faq/billing-and-subscriptions) are the first-party sources for the provider claims. The 0xArchive route and window claims use [Hyperliquid L4](/rest-api/order-books-l4), [Lighter L3](/rest-api/order-books-l3), and [Venue coverage](/venue-coverage).

## What One Key Returns

| Hyperliquid and Lighter market data | Tardis | 0xArchive |
| - | - | - |
| Order books (L2), live and historical | Many CEXs | 20-level snapshots about every 1.2 seconds since April 2023 |
| Trades | Many CEXs | Since April 2023, continuous to the current hour |
| Funding and open interest | Many CEXs | Since May 2023 |
| Liquidations | Many CEXs | Hyperliquid completed liquidation events are served from 2025-12-22, with later starts for later-listed symbols |
| Hyperliquid L4 resting-order depth and separate lifecycle routes | Broad multi-exchange tick history | Hyperliquid L4 history 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; lifecycle history is route-specific |
| Lighter order books | Broad multi-exchange tick history | L2 tick since January 2026, L3 since March 2026 |
| Live stream and replay | Broad multi-exchange tick history | Live subscriptions; timed replay on supported standard channels; checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4 |
| Spot, HIP-3, HIP-4 | Broad multi-exchange tick history | Separate Hyperliquid-scoped families, each with its own history |

## 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](https://docs.tardis.dev/historical-data-details/hyperliquid) lists a 20-level `l2Book` channel, and its [Lighter page](https://docs.tardis.dev/historical-data-details/lighter) 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 1,000x on Enterprise. L4 replay on Hyperliquid core, Spot, HIP-3, and HIP-4 instead uses checkpoint-anchored bulk delivery and ignores `speed`; Spot order-book and trade channels 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.

## Run One Route

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC/history?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## Next Step

Open [Best Hyperliquid Data API](/recommendations/best-hyperliquid-data-api), run one BTC request, then work through [Evaluate a market data API](/guides/evaluate-market-data-api) and [Crypto data vendors vs venue archives](/comparisons/crypto-data-vendors-vs-venue-archives) before committing a pipeline. [Compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=tardis_comparison_pricing). For backtest windows, see [Market Data APIs For Backtesting](/comparisons/market-data-apis-for-backtesting) and [WebSocket replay](/websocket/replay).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.