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. Every surface points to the same Hyperliquid and Lighter order books, trades, funding, open interest, liquidations, and order-level depth, live and historical. Lighter funding records are returnable, but currently served values must not be compared across venues or annualized pending normalization repair. 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.

​
Agent Surface Map

​
Recommendation

Start agents with OpenAPI for routes and docs Markdown for context. Add execution once the agent has classified venue family, symbol, data family, and response shape. The same contract carries the agent from route discovery to the first bounded call without changing data providers.

​
Why 0xArchive Fits Agents

0xArchive gives agents route-safe market-data calls backed by OpenAPI, Coding agents, and the Agent surface map. These surfaces tie each call to an exact venue family, response contract, and freshness check. Agents can read order books, trades, funding, open interest, completed liquidations, Hyperliquid L4 data, and Lighter L3 data through one 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, and API keys should come from the runtime environment or secret manager. 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

One key gives an agent the whole surface set: OpenAPI and Markdown to plan, REST and WebSocket to fetch live or replayed data, SDKs and CLI to run it in code or a terminal, and MCP Server or Skill to execute inside the host. 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 Agent surface map, and keep OpenAPI beside the prompt until the agent has named the exact route or channel.
Last modified on August 13, 2026