---
title: "AI Clients | 0xArchive Docs"
description: "Install 0xArchive via OpenClaw or a Claude Code skill for the fastest path, or MCP for typed tools in Claude Desktop, Cursor, and shared-client setups."
canonical_url: "https://www.0xarchive.io/docs/ai-clients/"
markdown_url: "https://www.0xarchive.io/docs/ai-clients.md"
route: "/docs/ai-clients"
robots: "index, follow"
generated_from: "prerendered_html"
---

# AI Clients

Use the Claude Code skill for the fastest setup. Use MCP when you want typed tools or shared client config.

Fastest Claude Code skill Structured MCP Separate topic Wallet automation

[Choose a setup](https://www.0xarchive.io/docs/ai-clients/#choose-path)

[Install options](https://www.0xarchive.io/docs/ai-clients/#claude-code)

Two good setups: the Claude Code skill if you want the quickest route from X-API-Key to a live answer, and MCP if you want typed tools or shared client config.

OpenClaw installs the skill. Start with a normal API key. Wallet Automation is the separate route when code has to sign up, mint or revoke keys, or renew paid access from a wallet.

## Pick a client setup

Choose by client shape and maintenance cost.

[Fastest setup Claude Code skill Fastest route from one API key to one live answer inside Claude Code. Best for Claude Code is the only client and you want the shortest path from X-API-Key to a real result. Do not use if You need the same typed tools across Claude Desktop, Cursor, or another MCP-capable client. Time to first result 2-5 minutes First command `openclaw install 0xarchive` Jump to Claude Code](https://www.0xarchive.io/docs/ai-clients/#claude-code)

[Shared tools MCP Typed tools across venue data, data quality, and wallet auth routes. Best for Typed tools, repeated use, or one local server shared across Claude Code, Claude Desktop, and Cursor. Do not use if Claude Code is the only target and you do not want to build or manage a local server process. Time to first result 5-10 minutes First command `npm run build` Jump to MCP](https://www.0xarchive.io/docs/ai-clients/#mcp)

## Get to the first answer

Install, expose the key, run one live query, and keep the simpler setup unless it stops fitting.

### Claude Code skill

Fastest route from API key to answer inside Claude Code.

1. 1 You Install the skill OpenClaw is the quick install. Plugin and standalone options are there when you want repo-backed or raw-file control. `openclaw install 0xarchive`
2. 2 You Expose the API key locally Set the same API key Claude Code will use so the skill can call live routes directly. `export OXARCHIVE_API_KEY=0xa_your_api_key`
3. 3 Claude Code Run one live query Start with one narrow market question so auth and transport are obvious. `/0xarchive:query BTC funding rate`
4. 4 0xArchive Check the first result You want real venue data or a direct auth/config error. If the answer is vague, fix setup first. Expect current or recent market data, or a direct configuration error you can act on.
5. 5 You Keep the simpler setup unless it stops fitting Stay on the skill unless typed tools or shared client config genuinely help. Use wallet automation when code has to mint or rotate keys itself.

### MCP

Best when you want typed tools or one config shared across clients.

1. 1 You Clone and build the MCP server Build the server locally once so the client can call the typed 0xArchive tools. `git clone https://github.com/0xArchiveIO/0xarchive-mcp.git && npm install && npm run build`
2. 2 MCP Server Register the server with your client Register it in user or local scope first. Project-wide installs can wait until the setup is boring. `claude mcp add 0xarchive -s user -t stdio ...`
3. 3 You Ask one narrow tool-backed question Start with a current query so auth, tool invocation, and output shape are easy to inspect. `"What's the current funding rate for BTC?"`
4. 4 0xArchive Check the tool output and schemas MCP should return a concrete tool result, not a prompt workaround. If it does not, fix scope or env vars. Expect a typed tool response with live venue data or a direct permission/configuration failure.
5. 5 You Set the install scope Keep experiments local. Move to project scope when the repo should carry the config, and share user-wide installs only after the team trusts the server.

## Scope and security

Keep install scope and trust decisions explicit. These clients get real tool access.

Scope

### Start local

Do not turn an untested install into a team-wide default. Get one clean result first, then decide where the config belongs.

Trust

### Treat tools like privileged code

Third-party MCP servers and skills can read, write, and act. Prompt injection and over-broad tool access are real risks.

Setup choice

### Skill for speed, MCP for structure

The Claude Code skill wins on setup time. MCP wins when typed tool families or shared config matter.

Separate job

### Wallet automation lives elsewhere

Start with a normal API key. If code has to self-provision, rotate keys, or renew paid access from a wallet, move to Wallet Automation instead of burying key lifecycle inside prompts.

## Claude Code install options

OpenClaw is the quick install. The plugin repo and standalone SKILL.md options give you more control.

OpenClaw install

Bash

```
openclaw install 0xarchive
```

Plugin install

Bash

```
git clone https://github.com/0xArchiveIO/0xarchive-skill.git
claude --plugin-dir ./0xarchive-skill
```

Standalone install

Bash

```
mkdir -p .claude/skills/0xarchive
curl -o .claude/skills/0xarchive/SKILL.md \
  https://raw.githubusercontent.com/0xArchiveIO/0xarchive-skill/main/skills/query/SKILL.md
```

## MCP install and registration

Build the server locally, then register it with the client that will hold the API key.

Build the local server

Bash

```
git clone https://github.com/0xArchiveIO/0xarchive-mcp.git
cd 0xarchive-mcp
npm install
npm run build
```

Claude Code registration

Bash

```
claude mcp add 0xarchive -s user -t stdio \
  -e OXARCHIVE_API_KEY=0xa_your_api_key \
  -- node /absolute/path/to/0xarchive-mcp/build/index.js
```

Claude Desktop registration

JSON

```
{
  "mcpServers": {
    "0xarchive": {
      "command": "node",
      "args": ["/absolute/path/to/0xarchive-mcp/build/index.js"],
      "env": {
        "OXARCHIVE_API_KEY": "0xa_your_api_key"
      }
    }
  }
}
```

## Reference comparison

Use this after you already know whether speed or typed tools matters more.

| Decision | MCP | Claude Code skill |
| --- | --- | --- |
| Dependencies | Node.js + npm | curl + jq |
| Compatible with | Claude Desktop, Claude Code, Cursor, any MCP client | Claude Code only |
| Tools | 79 typed tools with output schemas across venue data, data quality, and wallet auth | Natural language → curl commands |
| Use | Structured queries and multi-client setups | Fast setup when curl and jq are already available |

## What 0xArchive exposes through AI clients

Client choice changes ergonomics, not product coverage.

| Surface | Coverage |
| --- | --- |
| Hyperliquid | Instruments, L2/L4 order books, trades, candles, funding, open interest, liquidations, prices, summaries, freshness, order history, order flow, and TP/SL routes |
| HIP-3 | Instruments, order books, trades, candles, funding, open interest, liquidations, prices, summaries, freshness, order history, order flow, and TP/SL routes |
| Lighter.xyz | Instruments, L2/L3 order books, trades, candles, funding, open interest, prices, summaries, and freshness routes |
| Data Quality | GET /health, status, coverage, incidents, latency, and SLA monitoring utilities |
| Wallet / Web3 | SIWE challenge, wallet signup, key listing, key revoke, and x402 subscribe |

### Where to go next

[Wallet Automation Go here for wallet-managed signup, keys, and x402.](https://www.0xarchive.io/docs/wallet-automation/)

[CLI Use the API from shell scripts, cron, CI, or incident terminals.](https://www.0xarchive.io/docs/cli/)

[REST API Open route families, parameters, credits, and examples.](https://www.0xarchive.io/docs/rest-api/)