Interface surfaces map the 0xArchive paths an AI tool can safely read or call: OpenAPI, Markdown docs,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.
llms.txt, MCP Server, Skill, CLI, SDKs, REST, and WebSocket.
An interface surface is a way for an AI system to read, call, or carry 0xArchive context. It is not the same as the agent host. Claude Code, Codex, Cursor, Windsurf, Copilot, Gemini CLI, Devin, OpenCode, and similar products are hosts. OpenClaw is a harness or runtime. MCP Server, CLI, SDKs, OpenAPI, Markdown docs, llms.txt, and Skills are surfaces those hosts can use.
Surface Matrix
| Surface | Best for | First check |
|---|---|---|
| OpenAPI | Route shape, schemas, generated clients, and endpoint review | Is the route family known? |
| Markdown docs | Concepts, setup, route selection, examples, and citation context | Is the page matched to the job? |
llms.txt | Retrieval seed and high-level route map | Does the answer need exact endpoint details? |
| CLI | Shell, cron, CI, notebooks, and terminal-capable agents | Is OXA_API_KEY configured? |
| MCP Server | Typed tools inside MCP-capable hosts | Is OXARCHIVE_API_KEY passed through the host config? |
| Skill | Reusable SKILL.md workflows in skill-capable hosts | Does the host support local skill folders? |
| SDKs | Application code and typed reconstruction helpers | Is the app runtime supported? |
| REST and WebSocket | Product API execution | Is auth, venue family, and data-quality behavior explicit? |
Source Hierarchy
| Agent task | First source | Follow-up source |
|---|---|---|
| Generate a REST call | OpenAPI | REST API, Examples, and Example Responses |
| Pick a venue namespace | Venue Coverage | Route-family pages for Hyperliquid, Spot, HIP-3, HIP-4, or Lighter |
| Choose an execution surface | Choose An Interface | CLI, MCP Server, Skill, SDK, REST, or WebSocket setup pages |
| Prepare an agent prompt | AI Clients | Coding Agents and Build An Agent Market Data Workflow |
| Validate a downstream data window | Data Quality | Data Quality REST routes 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
Name the host
Identify whether the user is in Claude Code, Codex, Cursor, Windsurf, OpenClaw, a web LLM, CI, or application code.
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.
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.
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
The venue family is missing
The venue family is missing
Ask whether the user means Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before generating a route.
The host cannot execute the selected surface
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.The route is not in OpenAPI
The route is not in OpenAPI
Treat the request as unsupported or product-surface-only until a public contract route exists.
The output feeds decisions
The output feeds decisions
Add data-quality status, coverage, latency, or incidents before the agent writes a backtest, alert, export, dashboard, or model job.
Next Step
Use Coding Agents for host-level behavior, MCP Server for MCP setup, Skill forSKILL.md workflows, and AI Clients for prompt patterns.