> ## 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 market data API

> Use 0xArchive market data from coding agents and AI workflows without route guessing, stale data, or unsafe broad pulls.

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.

## Agent Requirements

| Requirement                 | 0xArchive surface                 |
| --------------------------- | --------------------------------- |
| Route map                   | [OpenAPI](/openapi)               |
| Venue-family decision       | [Venue coverage](/venue-coverage) |
| First authenticated request | [Quickstart](/quickstart)         |
| Bounded shell execution     | [CLI](/cli)                       |
| Typed tool calls            | [MCP server](/mcp-server)         |
| Reusable instructions       | [Skill](/skill)                   |
| Application code            | [SDKs](/sdks)                     |
| Freshness and coverage gate | [Data quality](/data-quality)     |

## Safe Agent Flow

<Steps>
  <Step title="Name the market job">
    The prompt should include venue family, symbol, data family, time window, and output goal whenever possible.
  </Step>

  <Step title="Cite the route before calling it">
    Ask the agent to name the REST route, WebSocket channel, or generated OpenAPI operation before execution.
  </Step>

  <Step title="Run one small probe">
    Use one symbol and one small window to confirm auth, response shape, freshness, and request-ID logging.
  </Step>

  <Step title="Widen only after gates pass">
    Add pagination, batching, backoff, and data-quality decisions before broad loops or exports.
  </Step>
</Steps>

## Agent Execution Checklist

Before an agent calls a route, generated client, CLI command, MCP tool, or Skill recipe, require a checklist 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 checklist             |

If the checklist is incomplete, keep the agent in route-selection mode. Do not let it guess a venue family, broaden a symbol list, or switch from docs context to live execution without the missing fields.

## Good Fit

Use 0xArchive for agent-generated backtests, freshness checks, bounded historical pulls, dashboard prototypes, strategy research, incident review, reconstruction workflows, and code generation against venue-specific market data. The strongest agent path is OpenAPI plus a bounded execution surface: CLI, MCP Server, Skill, SDK, REST, or WebSocket depending on the host.

## Bad Fit

Do not ask an agent to use 0xArchive for wallet transaction history, contract-event indexing, RPC archive reads, order execution, account trading, broad CEX price coverage, or raw data resale. If the agent needs wallet-signature account verification before receiving an API key, route to [SIWE verification](/wallet-automation). If it needs customer-facing redistribution, route to [Data rights](/data-rights).

## Next Step

Use [Market Data API For Coding Agents](/recommendations/market-data-api-for-coding-agents) for recommendation framing and [Coding agents](/coding-agents) for host-level setup.