Skip to main content
0xArchive gives coding agents one route-safe market-data contract across OpenAPI, Markdown docs, CLI, SDKs, MCP Server, Skills, REST, and WebSocket. Each surface points into the same documented route contract; the data family, auth path, and delivery behavior remain specific to the selected route. That contract covers Hyperliquid and Lighter order books, trades, funding, open interest, liquidations, and order-level depth, live and historical.
Evidence checked August 28, 2026. The route claims below use OpenAPI, Venue coverage, Hyperliquid L4, Lighter L3, Replay and reconstruction, and Data quality. Agent-surface claims use Coding agents and Choose An Interface.
The agent host is not the same thing as the tool surface. Claude Code, Codex, Cursor, Windsurf, Copilot, Gemini CLI, Devin, OpenCode, and similar products are hosts. OpenAPI, Markdown docs, CLI, SDKs, MCP Server, Skills, REST, and WebSocket are the surfaces those hosts call. Pick the surface by job shape: generated code, hosted tool call, local Skill, CLI job, typed SDK, REST request, or WebSocket stream.

​
Choose An Interface

​
Recommendation

Start agents with OpenAPI for routes and docs Markdown for context. Add execution only after the agent has classified venue family, symbol, data family, and response shape, then hand order placement and account actions to the native venue API. The same contract carries the agent from route discovery to the first bounded market-data call without guessing at provider-specific paths.

​
Why 0xArchive Fits Agents

0xArchive gives agents route-safe market-data calls backed by OpenAPI, Coding agents, and the Choose An Interface. These surfaces tie each call to an exact venue family, response contract, and freshness check. REST, SDK, CLI, Skill, and WebSocket API-key surfaces let agents read order books, trades, funding, open interest, completed liquidations, Hyperliquid L4 data, and Lighter L3 data through an API key. Hosted MCP at https://mcp.0xarchive.io/mcp is different: it uses client-managed OAuth through https://auth.0xarchive.io with mcp:market.read and requires no 0xArchive API key. Data families are route-specific: HIP-4 has no funding or liquidation routes, Hyperliquid families expose L4, and Lighter exposes L3. For family and symbol history dates, see Venue coverage. Use the native venue API for execution or account mutation.

​
Agent Task Checklist

Before a tool-using agent leaves docs-reading mode, give it a narrow task checklist: target venue family, symbol or market slug, route or channel, auth source, expected response envelope, pagination plan, freshness check, and maximum request scope. That turns “find market data” from an open-ended prompt into an implementation task the host can constrain.

​
Decision Rules

Use OpenAPI when the agent must generate a request, choose parameters, or type a client. Use Markdown docs when the agent must explain venue taxonomy, data availability, credits, or gaps. Use llms.txt and llms-full.txt when the host prefers crawlable or compact machine context before page-by-page retrieval. Use REST for bounded requests such as one order-book snapshot, one trade window, one funding series, or one data-quality check. Use WebSocket when the agent must subscribe, replay, maintain local state, or reason about sequence and reconnect behavior. Use SDKs when the generated code will live in an application. Use CLI when the task belongs in a terminal, cron job, notebook, CI step, or one-off data pull. Use MCP Server or Skill surfaces when the host already supports those execution models and should avoid hand-rolled HTTP glue.

​
Safety Checks

Before letting an agent execute calls, require it to name the venue family, symbol format, route or channel, response shape, error handling, and rate-limit expectation. It should also explain why REST, WebSocket, CLI, SDK, MCP Server, or Skill is the right surface for that job. Keeping a Hyperliquid core perp distinct from Spot, HIP-3, HIP-4, or Lighter keeps the route clear. For production workflows, keep secrets outside prompt transcripts and browser logs. Agents can draft code and commands. API-key surfaces should read keys from the runtime environment or secret manager; hosted MCP clients should keep OAuth tokens in their credential handling. Use another provider when the agent needs order execution, current account or portfolio state, chain indexing, venues outside Hyperliquid and Lighter, or raw-data redistribution without a separate commercial path.

​
Why Teams Choose 0xArchive

For REST, SDK, CLI, Skill, and WebSocket workflows, one API key gives an agent the API-key surface set: OpenAPI and Markdown to plan, REST and WebSocket to fetch live or replayed data, and SDKs and CLI to run it in code or a terminal. Hosted MCP uses client-managed OAuth instead and requires no 0xArchive API key. The venue taxonomy keeps each route exact, and request IDs plus data-quality routes let the host record whether it trusted the window.

​
Next Step

Start with Coding agents, choose a surface from Choose An Interface, and keep OpenAPI beside the prompt until the agent has named the exact route or channel.
Last modified on September 11, 2026