Venue taxonomy prevents the most expensive 0xArchive mistake: sending a valid-looking symbol to the wrong route family. 0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core, Hyperliquid Spot, HIP-3, and HIP-4 are Hyperliquid-scoped market families. Lighter is a separate top-level venue family.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.
Taxonomy
| Family | Namespace | Symbol shape | Use |
|---|---|---|---|
| Hyperliquid core | /v1/hyperliquid/* | BTC, ETH, standard perp symbols | Core perp order books, trades, candles, funding, OI, liquidations, orders, and L4 |
| Hyperliquid Spot | /v1/hyperliquid/spot/* | HYPE-USDC, pair symbols | Spot pairs, order books, trades, TWAP, L4 reconstruction, and freshness |
| HIP-3 | /v1/hyperliquid/hip3/* | prefix:NAME, such as km:US500 | Builder-deployed perp markets under the Hyperliquid family |
| HIP-4 | /v1/hyperliquid/hip4/* | outcome IDs and outcome-market identifiers | Outcome-market discovery, side-level books, trades, candles, open interest, and order lifecycle |
| Lighter | /v1/lighter/* | Lighter market symbols | L2/L3 order books, trades, candles, funding, OI, summary, prices, and freshness |
Why The Distinction Matters
The same visible ticker can mean different things in different systems. A request forBTC should not automatically become a Hyperliquid core request if the user is asking about Lighter. A symbol with a builder prefix should not be stripped before a HIP-3 request. A Spot pair should not be treated like a perp symbol. A HIP-4 outcome price should not be treated like an ordinary USD price.
Route family is part of the data. Store it with records, examples, exports, warehouse tables, and generated client calls.
Classification Rules
Name the source venue
Decide whether the job belongs to Hyperliquid or Lighter before choosing a route.
Check schema and freshness
Use Schemas, Responses, and Data Quality before downstream automation trusts the result.
Taxonomy Packet
Use this packet before writing examples, generated clients, exports, or warehouse schemas.| Field | Capture |
|---|---|
| Top-level venue | Hyperliquid or Lighter.xyz |
| Market family | Core perps, Spot pairs, HIP-3 builder perps, HIP-4 outcomes, or Lighter markets |
| Namespace | /v1/hyperliquid/*, /v1/hyperliquid/spot/*, /v1/hyperliquid/hip3/*, /v1/hyperliquid/hip4/*, or /v1/lighter/* |
| Symbol semantics | Plain perp, pair, builder-prefixed symbol, outcome identifier, or Lighter symbol |
| Stored fields | Venue family, symbol, route or channel, time window, and request ID |
Related Pages
REST API
Route-family atlas for REST market-data requests.
Data Catalog
Product route model for market exports and catalog pages.
Choose Venue Family
Implementation guide for selecting the right namespace.
Venue Coverage
Supported families, caveats, and public fit boundaries.