OpenClaw via Tokonomix

Add Tokonomix as a provider in openclaw.json — a privacy-first agent that owns its network path, now on 130+ models and consensus.

openai-completions providerPrivacy-first agent (CLI + VS Code)Open sourcemacOS · Windows · Linux

OpenClaw — privacy-first open-source agent, via Tokonomix

What is OpenClaw?

OpenClaw is a privacy-first open-source agent with guarded network paths — you control exactly where requests go. It declares model providers in openclaw.json, and any OpenAI-compatible endpoint is added with the openai-completions API type.

A CLI + VS Code agent built around an explicit, auditable network path.
Custom providers live under models.providers in openclaw.json.
Uses api: "openai-completions" for OpenAI-compatible endpoints.
Keys are referenced from environment variables.

Why route OpenClaw through Tokonomix?

OpenClaw’s trust model lines up with Tokonomix: you own the network path, and Tokonomix is one endpoint that fans out to 130+ models — with consensus and region routing for the calls where it matters.

Set tokonomix-consensus as the default for any planning task.
One provider, 130+ models, one key.
Per-call spend caps and hosting_region / origin_country routing.
Reference your key from an env var — nothing secret in the config file.

Connect Tokonomix in openclaw.json

Add a provider under models.providers with the Tokonomix baseUrl, an apiKey env reference and api: "openai-completions", then set it as the default model.

{
  "agents": {
    "defaults": { "model": { "primary": "tokonomix/tokonomix-consensus" } }
  },
  "models": {
    "providers": {
      "tokonomix": {
        "baseUrl": "https://tokonomix.ai/api/v1",
        "apiKey": "${TOKONOMIX_API_KEY}",
        "api": "openai-completions",
        "models": [
          { "id": "tokonomix-consensus", "name": "Tokonomix Consensus", "contextWindow": 200000 }
        ]
      }
    }
  }
}

Verify it works

Export TOKONOMIX_API_KEY and save openclaw.json.
Run a small task and confirm OpenClaw uses the Tokonomix model.
Confirm the call and token usage in your Tokonomix dashboard.

Model selection

Which model and endpoint should my agent use?

Pick by what your agent does, then swap the model id any time — every model in the catalog works through the same key.

What your agent does	Use this
Edits files / calls tools and streams responses (most coding agents)	An Anthropic model via the Anthropic endpoint (tools + streaming both work)
Calls tools but does not need streaming (any model)	The OpenAI-compatible endpoint with a single model id
Wants tools and streaming on a non-Anthropic model	Run non-streaming for now — streaming tool-calls on other providers is not enabled yet
Plain chat, no tools	Either endpoint; streaming is fine
Wants a cross-model verdict (consensus) on a high-stakes answer	Set model to tokonomix-consensus on the OpenAI-compatible endpoint — note: consensus rejects tool requests (no tool-calling)

Endpoint & API reference (technical)

anthropic-messages → https://tokonomix.ai/api/anthropic — tools ✓, streaming ✓ (use an Anthropic model). openai-completions → https://tokonomix.ai/api/v1 — tools ✓ (single-model passthrough), streaming with tools not yet enabled. Plain chat: streaming works on both. Consensus: openai-completions, model tokonomix-consensus, no tools. Swap the model id to any slug returned by GET /api/v1/models.

Browse all models →