> ## 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.

# Hydromancer Vs 0xArchive

> Compare Hydromancer with 0xArchive for live and historical Hyperliquid and Lighter books, trades, funding, OI, Hyperliquid L4, and Lighter L3.

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. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter: order-level depth, order lifecycle, and per-trade attribution across both venues, returned as normalized JSON from one key.

One call returns order books, trades, candles, funding, open interest, liquidations, and order-level (L4) depth. Hyperliquid order books and trades go back to April 2023. L4 order-level 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. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Lighter L3 depth begins in March 2026. 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.** Hydromancer's [Reservoir documentation](https://docs.hydromancer.xyz/reservoir) lists fills, candles, snapshots, and 20-level L2 snapshots at 1-minute cadence, delivered through requester-pays S3 with an August 2025 cutoff and daily updates. The cited Reservoir pages do not state Lighter L3 or historical Hyperliquid L4 order-level access. The 0xArchive route 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

| Market-data job | 0xArchive |
| - | - |
| Hyperliquid order books (L2), live and historical | 20-level snapshots about every 1.2 seconds since April 2023 |
| Hyperliquid L4 resting-order depth and separate lifecycle routes | 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 |
| Hyperliquid families | Core perps, Spot, HIP-3, and HIP-4, each its own route family with its own history |
| Lighter | Earliest observed trade row: January 17, 2025; exact starts vary by market. Funding and OI are recorded since August 2025. L3 starts March 2026. |
| Hyperliquid trades, funding, open interest, liquidations | Trades start April 2023; completed liquidations start at each symbol's `coverage_by_type.liquidations` date. |
| Live stream and replay | Live subscriptions; timed replay on supported standard channels; checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4 |
| Coverage, freshness, incidents, latency, gaps | One data-quality surface for each selected venue family |

## Where Hydromancer Fits

Hydromancer's [Reservoir documentation](https://docs.hydromancer.xyz/reservoir) lists a free, requester-pays S3 archive with fills, candles, snapshots, and 20-level L2 snapshots at 1-minute cadence. It states an August 2025 data cutoff and daily updates. Use Reservoir when a free Hyperliquid archive and that delivery shape are enough. The cited Reservoir page does not state Lighter L3 or historical Hyperliquid L4 order-level access, so 0xArchive is the better fit when the workload needs both venues, order-level grains, bounded REST history, or route-level quality checks. If the job is exploratory S3 access with 20-level L2 rather than a two-venue route contract, 0xArchive is not the right fit for that delivery shape.

A specialist archive can be a useful non-fit choice when cost and exploratory S3 access are the deciding axes. For a production workflow, compare the exact symbol window, order grain, update cadence, and recovery behavior before treating two archives as interchangeable.

## When To Use 0xArchive

One key spans both Hyperliquid and Lighter, with the deepest layer of each: full order-level L4 history on core and HIP-3 since March 2026, HIP-4 since May 2026, and Spot with separate order-event and reconstructable-checkpoint coverage checks; order-lifecycle history is route-specific, while Lighter L3 order-level depth starts in March 2026. The market data comes back normalized, with named fields, live or historical: Hyperliquid order-book records and trades back to April 2023. Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. 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.

## 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

Start with [Venue coverage](/venue-coverage), run one request against [Hyperliquid REST](/rest-api/hyperliquid), then add [Data quality](/data-quality). [Compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=hydromancer_comparison_pricing).


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