Supported Market Surfaces
| 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
0xArchive keeps market browsing and API implementation on the same taxonomy. The market page can introduce the instrument, but the implementation should still resolve through Venue coverage, REST API, Data quality, and the generated OpenAPI contract. That matters for Hyperliquid and Lighter work because a visual symbol is not enough. A useful market path names whether the job belongs to Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before it points to routes, exports, or code.What To Use First
| Reader job | Start here | Then verify |
|---|---|---|
| Browse supported markets | 0xArchive Data | Venue family, symbol, and available data families |
| Plan a route call | Matching instrument endpoint | REST API and generated OpenAPI |
| Build a chart or dashboard | Market page or Data explorer | Freshness, coverage, incidents, and API route support |
| Export files | Data catalog | Export schemas and Data rights |
| Generate client code | REST reference and OpenAPI | Examples, SDKs, and request IDs |
Market-To-API Checklist
Use this checklist to turn a market view into a working API call or export.| Your goal | Where to go |
|---|---|
| Confirm a market’s venue and route family | Venue coverage, then the matching REST family |
| Verify a symbol, pair, or outcome | The instrument, pair, or outcome route for that venue |
| Check freshness, incidents, or latency | Data quality |
| Pull files | Data catalog, Export schemas, Data rights |
| Write code | REST API, OpenAPI, Examples, SDKs |
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.Match it to the right route family
Resolve each market to its REST route family and confirm Data quality.
Confirm the market is implementation-ready
A market is ready to use when its venue family, symbol, freshness state, route support, and export or API path are all confirmed.
Respect data-rights boundaries
API access and exports do not grant raw redistribution rights. Check Data rights before any downstream delivery.