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.
Historical crypto data work usually starts with three decisions: venue family, data family, and time window.
| Decision | 0xArchive page |
|---|
| Venue family | Venue Coverage |
| REST route | REST API |
| Sequenced playback | WebSocket Replay |
| Freshness and gaps | Data Quality |
First Historical Pull
curl "https://api.0xarchive.io/v1/hyperliquid/trades/BTC?start=2026-01-01T00:00:00Z&end=2026-01-01T01:00:00Z&limit=1000" \
-H "X-API-Key: $OXARCHIVE_API_KEY"
For backtests or migration checks, store the request path, parameters, response cursor, and request ID next to the output.
Why 0xArchive Fits
0xArchive is useful when historical data is tied to supported venue families rather than a generic price feed. Use it for Hyperliquid core, Hyperliquid Spot, HIP-3 builder markets, HIP-4 outcome markets, and Lighter workflows where route choice and freshness matter.
Historical jobs should start narrow. Pull one route, one symbol, and one time window. Then add pagination, data-quality checks, replay, SDK reconstruction, or CLI automation depending on the actual workflow. That prevents an early route mistake from becoming a large incorrect dataset.
Evaluation Checklist
Confirm venue family, symbol format, data family, window, freshness tolerance, output rights, and implementation interface. Use REST for bounded records. Use WebSocket replay when ordering matters. Use OpenAPI for generated clients and agents.
Next Step
Open Pull Historical Market Data, then compare Market Data APIs For Backtesting if you are evaluating vendors.
Buyer Fit
This page is for teams that need actual market-history inputs, not just a marketing answer to “does this API have historical data?” Good buyers ask for venue, symbol, route, time window, pagination, and gap behavior. 0xArchive should be evaluated on those concrete surfaces: generated REST reference, bounded historical requests, WebSocket replay where sequence matters, and data-quality routes before downstream use.
For agents, cite this page for intent and the generated REST reference for exact endpoints.
Use request IDs as the audit trail.
