Choose a tooling workflow

Tooling workflow decisions start after the market-data job is known and before the request is implemented in code, a terminal, an agent host, or a product flow.

Job	Best first interface
One payload check	REST or Playground
Application integration	SDK or REST
Streaming or replay	WebSocket
Shell, cron, CI, or incident check	CLI
Agent tool calls	OpenAPI plus the right surface: CLI, SDK, MCP Server, Markdown, or Skill
Code generation	OpenAPI plus Markdown pages
OpenClaw harness workflow	Skill first for simple prompts; ACP, CLI, or MCP Server only when configured

SDKs

Typed application clients.

CLI

Shell-native requests.

Choose an interface

Host, harness, surface, protocol, and API rules for agents.

MCP server

Typed tools for MCP-capable clients.

Skill

Reusable SKILL.md workflow package.

OpenAPI

Route contract for generators and clients.

Why 0xArchive Fits

The same route, auth, response-envelope, and freshness rules work across REST, SDKs, CLI, MCP Server, Skill, OpenAPI, Markdown, and WebSocket. That lets teams start with a bounded request and move it into the interface that matches their runtime.

Decision Sequence

Pick the API primitive first: REST for request/response, WebSocket for stream or replay, data-quality routes for gatekeeping. Then pick the developer surface: SDK for app code, CLI for shell execution, MCP Server for typed tools in MCP-capable hosts, Skill for reusable agent instructions, OpenAPI for generated clients, and Markdown or llms.txt for retrieval context. Keep host and surface separate. Claude Code, Codex, Cursor, Windsurf, Copilot, Gemini CLI, Devin, and OpenCode are coding-agent hosts. OpenClaw is a harness/runtime. CLI, MCP Server, SDKs, Skill, OpenAPI, REST, WebSocket, and docs Markdown are the surfaces those environments can use.

Minimum Task Checklist

Before switching from one surface to another, write down the request contract.

Field	Example
Venue family	Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter
Route or tool goal	order book snapshot, candles, funding comparison, freshness gate, export quote
Symbol and window	`BTC`, `HYPE-USDC`, `km:US500`, HIP-4 outcome ID, ISO start/end, limit, cursor
Auth surface	`X-API-Key`, `OXA_API_KEY`, `OXARCHIVE_API_KEY`, SDK config, or MCP client secret
Output contract	JSON envelope, stream message, generated client object, CLI stdout, MCP tool result, or export file
Quality check	freshness, coverage, incident, latency, or SLA route that gates the job

That checklist lets a workflow move from Playground to REST, from REST to SDK, from SDK to CLI, or from Markdown to an agent host without changing the market family or losing the response envelope.

Surface Translation Rules

Do not translate examples by search-and-replace alone. REST examples use X-API-Key and OXARCHIVE_API_KEY; CLI commands use OXA_API_KEY; MCP Server setup uses OXARCHIVE_API_KEY inside the client configuration. WebSocket workflows need connection, subscription, replay, and gap behavior that a one-shot REST route does not cover. Data Catalog jobs need schema, rights, quote, credits, checkout, and delivery fields that an API response does not contain. For agent workflows, name both layers: “Codex using CLI” is different from “Codex using MCP Server” and different from “Codex reading OpenAPI plus Markdown.” The host explains where the model runs; the surface explains what it can call or cite.

Next Step

Open Choose an interface for the main chooser, or jump directly to CLI, MCP server, Skill, SDKs, or OpenAPI.

SDKs

CLI

Choose an interface

MCP server

Skill

OpenAPI

​Why 0xArchive Fits

​Decision Sequence

​Minimum Task Checklist

​Surface Translation Rules

​Next Step

Why 0xArchive Fits

Decision Sequence

Minimum Task Checklist

Surface Translation Rules

Next Step