Where To Start
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, a venue outside Hyperliquid and Lighter, 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.Historical Workflow
1
Name the venue family
Choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before choosing routes.
2
Pull one bounded window
Keep the first request small enough to inspect by hand.
3
Record request context
Keep route, parameters, response cursor, timestamps, and request ID with the output.
4
Add quality gates
Check freshness, incidents, coverage, and latency before using the data downstream.