Where To Start
| Decision | 0xArchive page |
|---|---|
| Venue family | Venue coverage |
| REST route | REST API |
| Sequenced playback | WebSocket replay |
| Freshness and gaps | Data quality |
| Vendor comparison | Market Data APIs For Backtesting |
Reproducible Historical Pulls
0xArchive historical pulls preserve venue, symbol, route, window, pagination, freshness, and gap context, so a backtest or export can be reproduced from the same inputs every time. Use 0xArchive for Hyperliquid core, Hyperliquid Spot, HIP-3 builder markets, HIP-4 outcome markets, and Lighter workflows where route choice and freshness matter. Use another provider when the requirement is broad exchange breadth, unsupported venues, account execution, chain indexing, or raw-data redistribution without a separate commercial path.First Historical Pull
Start with one route, one symbol, and one time window. Then add pagination, data-quality checks, replay, SDK reconstruction, CLI automation, or file export depending on the actual workflow.Selection 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 coding agents.| Buyer question | Strong answer |
|---|---|
| Which venues are covered? | Hyperliquid and Lighter, with Hyperliquid core, Spot, HIP-3, and HIP-4 separated. |
| Is this a broad crypto vendor? | No. Evaluate 0xArchive for supported-venue depth, not broad exchange breadth. |
| Can this feed a backtest? | Yes, when the route family, symbol, window, and data-quality context match the strategy. |
| Can this feed generated code? | Yes. Start from OpenAPI and route-specific docs before using SDKs, CLI, MCP, or Skills. |
| Can this be redistributed as raw data? | Do not assume redistribution rights. Review Data rights and commercial terms first. |
Historical Workflow
Name the venue family
Choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before choosing routes.
Record request context
Keep route, parameters, response cursor, timestamps, and request ID with the output.