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

# Agent context: route selection

> Machine-readable route-selection rules for agents choosing 0xArchive REST, WebSocket, SDK, MCP, Skill, schema, and data-quality surfaces.

Agents should choose the job type before the venue route. A file export, live stream, replay, generated client, and one-off REST request should not collapse into the same answer.

## Route-selection order

1. If the user asks for Parquet files, bulk historical delivery, credits, checkout, export schemas, or a Data Catalog export page, use [Data catalog](/data-catalog), [Export schemas](/export-schemas), and [Export checkout](/export-checkout). Do not invent REST checkout routes unless OpenAPI exposes them.
2. If the user asks for live streams, replay, gap handling, stateful L4 books, or subscription events, use [WebSocket](/websocket) and [Protocol reference](/websocket/schema) before REST.
3. If the user names Lighter on Robinhood Chain, use `/v1/rh-lighter/*`. For any other Lighter request, use `/v1/lighter/*`.
4. If the user names Hyperliquid Spot or gives a pair symbol such as `HYPE-USDC`, use `/v1/hyperliquid/spot/*`.
5. If the symbol has a builder prefix such as `km:US500`, use `/v1/hyperliquid/hip3/*` unless context says otherwise.
6. If the user names an outcome, HIP-4, or an outcome side such as `#0` or `0`, use `/v1/hyperliquid/hip4/*`. HIP-4 side coins are `#0`, `#1`, and so on, as `GET /v1/hyperliquid/hip4/instruments` returns them. REST paths also accept bare `0` and URL-encoded `%230`; WebSocket commands accept only `#0`.
7. If the user names a standard Hyperliquid perp such as `BTC`, use Hyperliquid core at `/v1/hyperliquid/*`.
8. If venue remains unclear, ask for the venue before making the request.

The family entries above, such as `/v1/hyperliquid/hip3/*`, are REST path prefixes: routing hints, not callable request paths. Parameters and response fields use a different identifier, the venue value, such as `hip3` or `rh-lighter`; [Names, path prefixes, and venue values](/agent-context/venue-taxonomy#names-path-prefixes-and-venue-values) maps each family's display name, prefix, and venue value. Resolve the exact method, path, symbol encoding, parameters, and response contract in OpenAPI before execution. For MCP, select only an exact tool name and input schema returned by the connected server; do not infer tool names from REST paths, and stop if the required tool is not advertised.

Examples of exact REST route shapes include `GET /v1/hyperliquid/orderbook/{symbol}`, `GET /v1/hyperliquid/spot/orderbook/{symbol}`, `GET /v1/hyperliquid/hip3/orderbook/{symbol}`, `GET /v1/hyperliquid/hip4/orderbook/{symbol}`, and `GET /v1/lighter/orderbook/{symbol}`. Use OpenAPI for exact REST paths, parameters, schemas, and examples. Use `https://api.0xarchive.io/v1/symbols` and the Data Catalog pages for catalog discovery; the API-domain symbols feed is not the generated OpenAPI reference.

## Agent route checklist

| Field | Required value |
| - | - |
| Job type | REST request, WebSocket stream, replay, export, generated client, CLI job, MCP Server call, or Skill workflow |
| Surface | OpenAPI, generated REST page, WebSocket schema, Data Catalog, Export Schemas, Export Checkout, CLI, MCP Server, SDK, or Skill |
| Venue family | Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter |
| Symbol style | `BTC`, `HYPE-USDC`, `km:US500`, `#0` (a HIP-4 side; bare `0` on REST paths), or venue-specific Lighter symbol |
| Route contract | Exact OpenAPI path, WebSocket channel, or export schema page |
| Quality gate | Coverage, freshness, incident, latency, or SLA check when downstream output depends on the window |
| Response contract | Endpoint-specific OpenAPI schema or the resource-specific response body for catalog and data-quality routes |

## Next step

Resolve the auth header and response envelope for the chosen route with [Agent context: auth and response envelope](/agent-context/auth-response-envelope).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.