Market Surfaces
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
Do not infer HIP-3, HIP-4, Spot, or Lighter availability from a category label. Confirm the symbol through the route family that will actually serve the request.
Market-To-API Checklist
Use this checklist to turn a market view into a working API call or export.From Market Page To API
1
Start from the instrument family
Use
/v1/hyperliquid/instruments, /v1/lighter/instruments, /v1/hyperliquid/hip3/instruments, or /v1/hyperliquid/hip4/instruments.2
Match it to the right route family
Resolve each market to its REST route family and confirm Data quality.
3
Confirm the route and window
Confirm the venue family, symbol, freshness state, route, and export or API path before the market feeds code or an export.
4
Respect data-rights boundaries
API access and exports do not grant benchmark, index, financial-product, standalone/substitute, raw-redistribution, white-label, or OEM rights. Check Data rights before those uses.