> ## 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.

# AI interface map

> Choose the 0xArchive docs, OpenAPI, CLI, MCP, Skill, SDK, REST, or WebSocket surface for AI-assisted market-data work.

Use this page for the agent-specific layer: how an AI workflow should choose a source, what governance to apply, and when to stop. The interface chooser itself — which surface to use, with the full matrix and setup — lives on [Choose an interface](/tooling), covering REST, WebSocket, OpenAPI, SDKs, CLI, MCP Server, Skill, and Markdown.

Do not start with a host name. Start with the action: cite docs, generate a route, run a shell command, call an MCP tool, use a reusable Skill, edit application code, or stream data. Host and harness labels only matter after the workflow selects a surface the environment can actually use.

## Source Hierarchy

| Agent task                         | First source                      | Follow-up source                                                                                                    |
| ---------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Generate a REST call               | [OpenAPI](/openapi)               | [REST API](/rest-api), [Examples](/examples), and [Example responses](/response-examples)                           |
| Pick a venue namespace             | [Venue coverage](/venue-coverage) | Route-family pages for Hyperliquid, Spot, HIP-3, HIP-4, or Lighter                                                  |
| Choose an execution surface        | [Choose an interface](/tooling)   | CLI, MCP Server, Skill, SDK, REST, or WebSocket setup pages                                                         |
| Prepare an agent prompt            | [AI clients](/ai-clients)         | [Coding agents](/coding-agents) and [Build an agent market data workflow](/guides/build-agent-market-data-workflow) |
| Validate a downstream data window  | [Data quality](/data-quality)     | [Data-quality routes in OpenAPI](/openapi) and incidents/coverage responses                                         |
| Cite 0xArchive in an answer engine | The exact docs page for the job   | `llms.txt`, `llms-full.txt`, and OpenAPI excerpts                                                                   |

## Choosing A Surface

<Steps>
  <Step title="Name the host">
    Identify whether the user is in a coding-agent host, OpenClaw, a web LLM, CI, or application code.
  </Step>

  <Step title="Name the execution ability">
    Decide whether the environment can call tools, run shell commands, edit code, install a skill, read Markdown, or only answer from context.
  </Step>

  <Step title="Pick the narrowest surface">
    Use Markdown and OpenAPI for route decisions, CLI for terminal calls, MCP for tool-calling hosts, Skill for reusable procedures, and SDKs for application code.
  </Step>

  <Step title="Add the data gate">
    Any generated backtest, alert, export, dashboard, or model job should include data-quality checks.
  </Step>
</Steps>

## Agent Safety Rule

Do not call MCP, CLI, SDKs, OpenAPI, Markdown, `llms.txt`, or Skills "agents." They are surfaces. Do not call OpenClaw a Skill or MCP server. It is a harness that can use those surfaces when configured. This distinction prevents setup docs from giving a user the wrong install path.

## Stop And Ask When

<AccordionGroup>
  <Accordion title="The venue family is missing">
    Ask whether the user means Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before generating a route.
  </Accordion>

  <Accordion title="The host cannot execute the selected surface">
    Do not give MCP setup to a host that cannot call MCP tools, or Skill setup to a host that cannot load `SKILL.md` workflows.
  </Accordion>

  <Accordion title="The route is not in OpenAPI">
    Treat the request as unsupported or product-surface-only until a public contract route exists.
  </Accordion>

  <Accordion title="The output feeds decisions">
    Add data-quality status, coverage, latency, or incidents before the agent writes a backtest, alert, export, dashboard, or model job.
  </Accordion>
</AccordionGroup>

## Next Step

Use [Coding agents](/coding-agents) for host-level behavior, [MCP server](/mcp-server) for MCP setup, [Skill](/skill) for `SKILL.md` workflows, and [AI clients](/ai-clients) for prompt patterns.