Run OpenClaw on any model

Open-source autonomous agent runtime - register Antseed as a custom provider in openclaw.json.

Autonomous agentsAnthropic Messages~3 min

What OpenClaw is. OpenClaw is an open-source agent runtime for autonomous, long-running tasks (research, coding, web automation). It loads its provider catalog from ~/.openclaw/openclaw.json - each entry is an HTTP endpoint plus a wire protocol (anthropic-messages, openai-chat, etc.) and a list of models.

How Antseed plugs in. Add a provider entry called antseed with api: "anthropic-messages" and authHeader: true. Use http://127.0.0.1:8377/v1 when OpenClaw runs beside the AI VPN. When it runs elsewhere, expand AI VPN → Agents → Define your internet-accessible Antseed endpoint, start ngrok or Cloudflare, and copy the displayed URL and API key.

Why a config entry instead of env vars. OpenClaw runs many providers in parallel (one per task, sometimes one per agent). A single base-URL override would force every agent through Antseed; a named provider lets you mix Antseed with hosted Anthropic, OpenAI, or local models on a per-agent basis.

Run Antseed first

Every integration assumes a buyer proxy at http://localhost:8377. One-time setup, ~2 minutes.

Step 1

Install OpenClaw

Install OpenClaw
npm install -g openclaw
Verify with openclaw --version. OpenClaw has a newer Node.js support policy than Antseed, so use a Node version accepted by the current OpenClaw release. The config file lives at ~/.openclaw/openclaw.json and is created on first launch.

Step 2

Point OpenClaw at Antseed

ANTSEED_BASE_URL	http://127.0.0.1:8377/v1
ANTSEED_API_KEY	antseed-p2p

Show as shell exports

export ANTSEED_BASE_URL="http://127.0.0.1:8377/v1" export ANTSEED_API_KEY="antseed-p2p"

Local setup: keep these defaults. Remote setup: in AI VPN → Agents, expand “Define your internet-accessible Antseed endpoint,” start ngrok or Cloudflare, then replace both values with the displayed URL and generated antseed_... key.

~/.openclaw/openclaw.json (merge into the existing `models.providers` object)

{ "models": { "providers": { "antseed": { "baseUrl": "${ANTSEED_BASE_URL}", "apiKey": "${ANTSEED_API_KEY}", "authHeader": true, "api": "anthropic-messages", "models": [ { "id": "antseed", "name": "Current AI VPN selection", "reasoning": false, "input": ["text"], "contextWindow": 128000, "maxTokens": 8192 }, { "id": "kimi-k2.6", "name": "Kimi K2.6 (via Antseed)", "reasoning": false, "input": ["text"], "contextWindow": 256000, "maxTokens": 8192 }, { "id": "deepseek-v4-flash", "name": "DeepSeek v4 Flash (via Antseed)", "reasoning": false, "input": ["text"], "contextWindow": 128000, "maxTokens": 8192 } ] } } } }

# Follow the current AI VPN model picker for new agents: openclaw models set "antseed/antseed"

Step 3

Pick a model

kimi-k2.6deepseek-v4-flashminimax-m2.7gpt-oss-120b

The special antseed id follows the current AI VPN model picker. Every other id under models[] must match a model id from GET /v1/models. Keep authHeader: true: OpenClaw otherwise uses Anthropic-native authentication, while the public Antseed gateway requires Authorization: Bearer <API_KEY>. Route to a specific peer with <peerId>@<service-id>.

The full list is every model on the network. Run curl -s localhost:8377/v1/models, antseed network browse, or open the live network page to see what's available right now.

Verify

Test it

Confirm the proxy advertises the model ids you put in config
curl -s "$ANTSEED_BASE_URL/models" -H "Authorization: Bearer $ANTSEED_API_KEY" | jq '.data[].id'
Example response
"deepseek-v4-flash" "gpt-oss-120b" "kimi-k2.6" "minimax-m2.7"
If a model id you listed in openclaw.json doesn't appear here, no peer on the network currently serves it. Remove the entry or pick another model from the list.
Check the configured model catalog
openclaw models list
Run openclaw gateway restart after editing the config. You should see the antseed provider and its configured models.
Run an agent against Antseed
openclaw agent exec "Summarize the README in this repo" --model antseed/kimi-k2.6

How OpenClaw talks to Antseed

Wire format sent by OpenClaw: Anthropic Messages (hits /v1/messages on the buyer proxy)
Best-fit services: any service whose protocols array contains anthropic-messages. That's what the peer advertises as natively-supported - zero translation overhead, no transform edge cases.
How to check a peer: run antseed network peer <peerId> --json and look at providerServiceApiProtocols[provider].services[service]. The browse command exposes the same field per peer.
What happens when protocols don't match: Antseed's @antseed/api-adapter translates between Anthropic Messages and the service's native protocol on the fly. So a request from OpenClaw can still reach a service that only advertises openai-chat-completions - just with a small transform step.
One known caveat: services whose only advertised protocol is openai-responses require streaming. If OpenClaw sends a non-streaming request and the proxy routes it to one of those services, the call fails with HTTP 400: Stream must be set to true. Pick a service whose protocols includes anthropic-messages (or another non-responses protocol) to avoid this.

If it goes wrong

Troubleshooting

provider "antseed" not found when launching an agentJSON parse error in openclaw.json, or you put the entry in the wrong nesting level. The provider must live under models.providers.antseed. Run openclaw config validate to surface parse errors.
OpenClaw lists antseed/<id> but every call returns 502 model_not_foundNo policy-allowed peer currently advertises that model. Check GET $ANTSEED_BASE_URL/models with the bearer key and update models[], or pick another model.
Streaming errors on long-running agentsAntseed supports SSE streaming. If you see truncated responses, check that no proxy in front of OpenClaw is buffering (Cloudflare, nginx). The buyer proxy itself does not buffer.
Agent stalls on first request after a deployAntseed opens a payment channel on the first request to a new peer (one on-chain transaction, ~5–15s on Base). Subsequent requests reuse the channel. Pre-warm by running a quick curl before launching the agent.
OpenClaw runs remotely and cannot reach 127.0.0.1:8377Open AI VPN → Agents, expand “Define your internet-accessible Antseed endpoint,” and start ngrok or Cloudflare. Put the displayed /v1 URL in ANTSEED_BASE_URL, the generated key in ANTSEED_API_KEY, and keep authHeader: true. Do not expose port 8377 directly.

Reference

Links

OpenClaw repo OpenClaw model-provider docs Antseed skill: openclaw-antseed (full walkthrough)Antseed Agents guide Antseed Public HTTPS Tunnels guide

Same category

Hermes All integrations