What One Key Returns
| Hyperliquid market data | 0xArchive |
|---|---|
| Order books (L2), live and historical | 20-level snapshots about every 1.2 seconds since April 2023, 24.6B+ records, 176 symbols |
| Trades | Since April 2023, continuous to the current hour |
| Funding and open interest | Since May 2023 |
| Liquidations | Since December 2025 |
| Order-level depth (L4) and lifecycle | Every order add, fill, cancel, and TP/SL, with wallet attribution, since March 2026 |
| Live stream and replay | WebSocket subscriptions and exact-window replay on one socket |
| Spot, HIP-3, HIP-4 | Separate route families, each with its own history |
Where The Native API Fits
0xArchive does not place orders; execution belongs to the venue’s own API, and for that job the native endpoint is the only correct choice. Order placement, cancels, and account state live on the exchange endpoint, signed by your wallet. The info endpoint also answers live market questions well: current mids for every coin, a 20-levell2Book snapshot, recent trades, and funding history, all free and venue-native.
The bounds show up when the question is historical, and Hyperliquid’s own docs state them: candleSnapshot returns only the most recent 5,000 candles, userFills returns at most 2,000 recent fills, userFillsByTime reaches only the 10,000 most recent, time-range responses page at 500 elements, and l2Book is a live snapshot with no historical form. There is no request that returns the book as it stood last Tuesday. If the job is execution or reading your own account, 0xArchive is not the right fit; that stays on the venue. If the job is a backtest, a research window, or anything older than those retention caps, the native API cannot answer it.
When To Use 0xArchive
One call replaces a collector you would otherwise build and run against those retention caps. The market data comes back normalized, with named fields, live or historical: more than 24 billion order-book records and trades back to April 2023, plus full order-level (L4) depth with wallet attribution since March 2026. Every response carries a request ID and a data-quality path you can check before a backtest trusts the window. Access follows the key, not the plan: every route, market family, and schema is available on every tier, including Free; plans change credits, request rate, and replay speed, which scales from 10x to 300x by plan and up to 500x on Enterprise. Agents read the same surface through the hosted MCP server athttps://mcp.0xarchive.io/mcp, a remote endpoint that takes your API key as a bearer token, nothing to install. Every order, trade, and fill. One API.