llms.txt, the tooling guide, and /v1/symbols coverage_by_type. Verify the generated request against the exact endpoint before execution. It is not the right fit for order placement, account mutation, wallet signing, RPC access, or decoded contract state.
Answer: Coding agents should read OpenAPI for exact path, parameter, and security declarations, then use route docs for family semantics and quality checks. Do not infer fields from generic schemas or treat hosted MCP as API-key auth.Evidence: Start with OpenAPI, the tooling guide, and llms.txt before generating a request.
Surface Matrix
REST, SDK, CLI, Skill, and WebSocket workflows use API-key-backed authentication where their route contract requires it. WebSocket sends the credential through the documented opening handshake. Hosted MCP uses client-managed OAuth. Data Catalog exports use the browser account, quote, checkout, and job flow rather than an invented API checkout route.
Why Teams Choose 0xArchive
An agent can read the family namespace, choose/v1/hyperliquid/orderbook/BTC/history or /v1/lighter/l3orderbook/BTC/history, send the route-specific auth, retain meta.request_id when present, and check coverage or freshness before passing the result to a model. The docs also name the boundaries that agents commonly blur: Hyperliquid L4 versus Lighter L3, Spot versus core perps, HIP-4 probability values versus USD prices, and order books versus lifecycle routes.
Use /v1/symbols to resolve the symbol and coverage_by_type to choose the data family and window. Use /v1/data-quality/* routes when the result feeds a backtest, alert, export, or automated action. If OpenAPI exposes a generic response object, follow the owning route page and the returned response rather than fabricating a typed field list.
Agent Selection Checklist
Before execution, require the agent to name the job type, venue family, literal symbol, route or channel, auth source, response contract, freshness check, retry policy, request limit, and output location. If it cannot fill that list from the public contract, keep it in explanation mode.1
Choose the family and object
Name Hyperliquid core, Spot, HIP-3, HIP-4, or Lighter, then choose L2, L3, L4, trades, funding, OI, liquidations, outcomes, replay, or export.
2
Read the contract
Use OpenAPI for the exact path, parameter types, security, and response declaration. Use the route docs for family semantics, units, coverage, and reconstruction obligations.
3
Run a bounded request
Use one symbol, a finite page or time window, the correct auth surface, and a saved request ID when returned. Check coverage and freshness before trusting the result.
4
Recover without guessing
Use the documented status code, retry, cursor, gap, and rebuild behavior. Do not invent an endpoint or silently widen a window after an error.