Market pages are chart-first entry points, but they still map back to 0xArchive venue families, symbol rules, API routes, exports, and data-quality checks. The live product surface for browsing data is 0xArchive Data. Market-specific pages should point to the same public taxonomy as the API portal: venue family, route family, freshness, API CTA, and data-rights boundaries.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.
Current Bridge
| Surface | Status | Use it for |
|---|---|---|
| Data explorer | Live | Browse supported market data visually |
/v1/hyperliquid/instruments | In OpenAPI | Hyperliquid core instrument planning |
/v1/lighter/instruments | In OpenAPI | Lighter instrument planning |
/v1/hyperliquid/hip3/instruments | In OpenAPI | HIP-3 instrument planning |
/v1/hyperliquid/hip4/instruments | In OpenAPI | HIP-4 instrument and outcome-market planning |
Why 0xArchive Fits
Chart-first market pages and API docs should not tell different stories. 0xArchive keeps the market-page bridge anchored to the same route families developers use: Venue Coverage, REST API, Data Quality, and the generated OpenAPI reference. That means a market page can point a builder from a visual chart to the exact API route family without inventing a separate taxonomy.Page Selection Rule
Link a market-specific page when it has live chart data, symbol evidence, freshness context, route links, and a useful API next step. Use the Data explorer when the user needs the current browsing surface, and use the REST reference when the user needs implementation details. Do not infer HIP-3 or RWA-style coverage from category language. Symbol pages must be grounded in live API behavior and the instrument route family.Market Bridge Packet
Use this packet when moving from a chart-first market view into developer docs or API usage.| Market-page signal | Required next step |
|---|---|
| Venue family is visible | Link the matching Venue Coverage section and REST family. |
| Symbol or pair is visible | Confirm it through the relevant instrument, pair, or outcome route before publishing route examples. |
| Freshness or outage context matters | Attach Data Quality, freshness, incident, or latency context. |
| The reader wants files | Send them to Data Catalog, Export Schemas, and Data Rights. |
| The reader wants code | Send them to REST API, OpenAPI, Examples, or SDKs. |
| Market-detail URLs are not exposed on the website | Link the Data explorer and docs pages, not undeployed detail paths. |
From Market Page To API
Start from the instrument family
Use
/v1/hyperliquid/instruments, /v1/lighter/instruments, /v1/hyperliquid/hip3/instruments, or /v1/hyperliquid/hip4/instruments.Attach the correct docs path
Link each chart page to the right REST family and Data Quality.
Use pages with enough context
A useful market page should show chart data, route support, freshness state, an API next step, and a reason the market matters.