Data availability is not a yes/no claim until the venue family, symbol, data family, time window, freshness tolerance, and plan access are named. Availability is not one global yes or no. A market can have current order-book data but a shorter historical window for another data family. A route can be valid while a specific symbol or time range is not useful for a downstream job. Treat availability as a preflight step, not as a marketing claim.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.
Availability Dimensions
| Dimension | Question to answer | Where to check |
|---|---|---|
| Venue family | Is this Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter? | Venue Coverage |
| Symbol | Is the exact symbol or pair supported in that family? | Instrument or coverage routes |
| Data family | Do you need order books, trades, candles, funding, OI, liquidations, L3, L4, replay, or freshness? | REST API and OpenAPI |
| Time window | Is the requested window inside available history? | Data-quality coverage and small probe requests |
| Freshness | Is the latest ingestion state acceptable for the job? | Data Quality |
| Access tier | Is the route or volume allowed for the current key? | Rate Limits |
Preflight Pattern
Name the route family
Write the family in the job config before writing the endpoint. For example,
hyperliquid_spot and hyperliquid_core should not collapse into one label.Probe one exact market
Call one instrument, coverage, freshness, order-book, or trade route for the exact symbol before looping over symbols.
Check the data family
Confirm that the requested data family exists for the route. L4, L3, replay, funding, and open-interest coverage can have different constraints.
Common Mistakes
Do not infer support from a category name. A phrase such as “RWA market”, “Spot pair”, or “outcome market” still needs a route-family and symbol check. Do not treat a successful latest snapshot as evidence that every historical window exists. Do not hide a freshness or incident warning from downstream systems just because the API returned a payload. If a route returns a valid response but the freshness or coverage state is outside tolerance, mark the output incomplete or stop the job. That is especially important for backtests, alerts, exports, and model features, where bad data can look like a real market signal.Availability Packet
For every availability answer, capture the exact venue family, symbol, data family, UTC window, freshness tolerance, access tier, and first probe result. If the answer cannot name those fields, it is only a category-level guess.| Packet field | Example |
|---|---|
| Route family | hyperliquid_spot, hip3, hip4, lighter |
| Symbol | HYPE-USDC, km:US500, HIP-4 outcome ID, or Lighter BTC |
| Data family | Trades, candles, order book, L3, L4, funding, OI, replay, or export |
| Gate | Coverage, freshness, incident, latency, route access, or bounded probe |