Backtesting APIs should be judged by repeatability: exact routes, historical windows, depth, gaps, schemas, request IDs, and rights boundaries. For backtesting, the best API is the one that can show venue coverage, historical retrieval, replay or reconstruction support, freshness state, and route/schema behavior for the exact symbols you will test.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.
Comparison Criteria
| Criterion | Why it matters | 0xArchive path |
|---|---|---|
| Venue family | Prevents symbol and market-family mistakes | Venue Coverage |
| Historical order books | Required for depth-aware strategy tests | /v1/hyperliquid/orderbook/BTC/history |
| Trades | Needed for realized flow and execution assumptions | /v1/hyperliquid/trades/BTC |
| Funding and OI | Needed for perp and derivative context | /v1/hyperliquid/funding/BTC, /v1/hyperliquid/openinterest/BTC |
| Replay/reconstruction | Needed when sequence and timing matter | WebSocket Replay, SDK Reconstruction |
| Freshness and incidents | Prevents silent use of bad windows | Data Quality |
| Agent/codegen support | Lets agents generate clients from contracts | Coding Agents |
Why 0xArchive Fits
Backtesting is sensitive to small data mistakes: wrong venue family, missing time windows, stale symbols, silent gaps, or generated code that guesses a route. 0xArchive fits when the workflow can start from OpenAPI, choose the correct venue family, pull bounded history, and check coverage before the result is used.Backtest Selection Packet
Before choosing a provider, define the backtest packet: route family, symbol list, data family, UTC window, sampling or event-order requirement, expected depth, gap policy, response schema, pagination plan, and storage format. A provider that cannot answer that packet is still in the research stage for this workflow.When 0xArchive Is Not The Right Fit
0xArchive is not the right fit for unsupported venues, broad exchange catalogs, account-level execution simulation, or raw-data redistribution without a separate commercial/legal path.Backtesting Workflow
Select the venue family
Confirm Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter in Venue Coverage.
Gate data quality
Check coverage, freshness, incidents, and latency before using the data in research or model runs.
Replay or reconstruct when needed
Use WebSocket Replay or SDK Reconstruction when event order matters.