> ## 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.

# Markets and chart pages

> Connect 0xArchive market pages, the live data explorer, instrument routes, venue coverage, freshness checks, and API docs.

Turn any 0xArchive market view into an API request, export, chart, or build task.

Every 0xArchive market resolves to a venue family, symbol format, route family, freshness state, and output boundary — so you can move from a chart to a working API call without guessing. Start from the live [0xArchive Data](https://0xarchive.io/data?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=markets_intro) surface to browse covered markets, then move to the matching instrument and REST routes for implementation detail.

## Supported Market Surfaces

| Surface                                                                                                                                        | Status     | Use it for                                   |
| ---------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------------------------------------------- |
| [Data explorer](https://0xarchive.io/data?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=markets_surface_table) | 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](/venue-coverage), [REST API](/rest-api), [Data quality](/data-quality), and the generated [OpenAPI](/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](https://0xarchive.io/data?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=markets_decision_table) | Venue family, symbol, and available data families                 |
| Plan a route call          | Matching instrument endpoint                                                                                                                     | [REST API](/rest-api) and generated [OpenAPI](/openapi)           |
| Build a chart or dashboard | Market page or Data explorer                                                                                                                     | Freshness, coverage, incidents, and API route support             |
| Export files               | [Data catalog](/data-catalog)                                                                                                                    | [Export schemas](/export-schemas) and [Data rights](/data-rights) |
| Generate client code       | REST reference and OpenAPI                                                                                                                       | [Examples](/examples), [SDKs](/sdks), and request IDs             |

Do not infer HIP-3, HIP-4, Spot, or Lighter support 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.

| Your goal                                 | Where to go                                                                                   |
| ----------------------------------------- | --------------------------------------------------------------------------------------------- |
| Confirm a market's venue and route family | [Venue coverage](/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](/data-quality)                                                                 |
| Pull files                                | [Data catalog](/data-catalog), [Export schemas](/export-schemas), [Data rights](/data-rights) |
| Write code                                | [REST API](/rest-api), [OpenAPI](/openapi), [Examples](/examples), [SDKs](/sdks)              |

## From Market Page To API

<Steps>
  <Step title="Start from the instrument family">
    Use `/v1/hyperliquid/instruments`, `/v1/lighter/instruments`, `/v1/hyperliquid/hip3/instruments`, or `/v1/hyperliquid/hip4/instruments`.
  </Step>

  <Step title="Match it to the right route family">
    Resolve each market to its REST route family and confirm [Data quality](/data-quality).
  </Step>

  <Step title="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.
  </Step>

  <Step title="Respect data-rights boundaries">
    API access and exports do not grant raw redistribution rights. Check [Data rights](/data-rights) before any downstream delivery.
  </Step>
</Steps>

## Data-Rights Boundary

API access and exports do not automatically grant raw redistribution rights for the underlying archive. Review [Data rights](/data-rights) before any downstream delivery, public download, or partner workflow.

## Next Step

Open the live [Data explorer](https://0xarchive.io/data?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=markets_next_step), then use [Venue coverage](/venue-coverage) and [REST API](/rest-api) to move from visual inspection to API usage.