An agent market data API needs stricter routing than a generic coding-agent setup page: the agent needs market data, and the docs must stop it from guessing routes or running unsafe calls. 0xArchive fits agent workflows when the task is supported venue market data across Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter. It should not be framed as a broad CEX catalog, onchain wallet indexer, RPC provider, execution API, or raw-data redistribution product.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 Requirements
| Requirement | 0xArchive surface |
|---|---|
| Route map | OpenAPI |
| Venue-family decision | Venue Coverage |
| First authenticated request | Quickstart |
| Bounded shell execution | CLI |
| Typed tool calls | MCP Server |
| Reusable instructions | Skill |
| Application code | SDKs |
| Freshness and coverage gate | Data Quality |
Safe Agent Flow
Name the market job
The prompt should include venue family, symbol, data family, time window, and output goal whenever possible.
Cite the route before calling it
Ask the agent to name the REST route, WebSocket channel, or generated OpenAPI operation before execution.
Run one small probe
Use one symbol and one small window to confirm auth, response shape, freshness, and request-ID logging.
Agent Execution Packet
Before an agent calls a route, generated client, CLI command, MCP tool, or Skill recipe, require a packet with the fields below.| Field | Example |
|---|---|
| Venue family | Hyperliquid core, Spot, HIP-3, HIP-4, or Lighter |
| Symbol or market | BTC, HYPE-USDC, km:US500, or a HIP-4 outcome identifier |
| Data family | Order book, trades, candles, funding, OI, liquidations, L3, L4, freshness, or export |
| Execution surface | REST, WebSocket, CLI, SDK, MCP Server, Skill, or Data Catalog |
| Request bound | One route, one symbol, one small window, or one page before widening |
| Quality gate | Coverage, freshness, incident, latency, request ID, or replay-gap check |
| Output owner | Notebook, script, app, dashboard, model, warehouse, or support packet |