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
- If the user asks for Parquet files, bulk historical delivery, credits, checkout, export schemas, or a Data Catalog export page, use Data catalog, Export schemas, and Export checkout. Do not invent REST checkout routes unless OpenAPI exposes them.
- If the user asks for live streams, replay, gap handling, stateful L4 books, or subscription events, use WebSocket and Protocol reference before REST.
- If the user names Lighter on Robinhood Chain, use
/v1/rh-lighter/*. For any other Lighter request, use /v1/lighter/*.
- If the user names Hyperliquid Spot or gives a pair symbol such as
HYPE-USDC, use /v1/hyperliquid/spot/*.
- If the symbol has a builder prefix such as
km:US500, use /v1/hyperliquid/hip3/* unless context says otherwise.
- 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.
- If the user names a standard Hyperliquid perp such as
BTC, use Hyperliquid core at /v1/hyperliquid/*.
- 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 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
Next step
Resolve the auth header and response envelope for the chosen route with Agent context: auth and response envelope. Last modified on October 6, 2026
