Data Families
Venue Scope
0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core, Hyperliquid Spot, HIP-3, and HIP-4 are separate Hyperliquid-scoped market families. Lighter routes live under/v1/lighter/*.
Do not flatten those families in a data model. Store venue family, symbol, route, time window, and request ID with the records. A BTC perp record, a HYPE-USDC Spot pair, a km:US500 HIP-3 symbol, a HIP-4 outcome side, and a Lighter symbol should stay distinguishable in storage, examples, and generated code.
Data Routing Checklist
Use this checklist when the request starts from broad data intent instead of a concrete endpoint.Data Workflow
1
Choose venue family
Use Venue coverage before choosing a REST path or WebSocket channel.
2
Confirm data availability
Check instruments, pairs, outcomes, coverage, or freshness before running wide historical jobs.
3
Inspect schema and response shape
Use Schemas, Responses, and Export schemas before parsing fields into typed code or warehouse tables.
4
Run a bounded example
Use Examples with one symbol and one small window before widening.
5
Check rights before redistribution
Use Data rights before creating benchmarks, indices, or financial products, or publishing bulk raw-data downloads, bulk republication, resale, API mirrors, substitute feeds, or white-label or OEM delivery.