OpenClaw
Route OpenClaw agent requests through BitRouter in under 2 minutes
BitRouter plugs into OpenClaw as a native plugin. Install it, pick a provider, and every agent request routes through BitRouter automatically — with failover, load balancing, guardrails, and usage metrics out of the box.
Install the Plugin
openclaw plugins install @bitrouter/openclaw-pluginChoose Your Provider
Pay-per-token via an on-chain Swig wallet. No API keys to manage — BitRouter handles provider access for you.
openclaw bitrouter setupThis launches an interactive wizard that creates a Swig wallet and completes onboarding. Once finished:
openclaw gateway restartUse your existing OpenRouter, OpenAI, or Anthropic API key.
openclaw models auth login --provider bitrouterThe wizard prompts you to pick an upstream provider and enter your key. Once finished:
openclaw gateway restartZero-config shortcut: If OPENAI_API_KEY, ANTHROPIC_API_KEY, or OPENROUTER_API_KEY is already in your environment, BitRouter auto-detects it. You can skip this step entirely.
Route Your Agents
By default, the plugin only intercepts models with explicit routing rules. Run switch-all to rewrite every agent's model config so all requests flow through BitRouter:
openclaw bitrouter switch-all
openclaw gateway restartTo undo at any time: openclaw bitrouter restore-models && openclaw gateway restart
Verify
openclaw bitrouter statusYou should see the daemon marked as healthy, your configured routes listed, and wallet info if you're using Cloud mode.
What You Get
- Failover & load balancing — priority or round-robin routing across providers. Learn more
- Agentic identity & payment — scoped on-chain spending via Swig with per-agent budgets. Learn more
- Guardrails — redact or block sensitive data (API keys, PII) in transit
- Usage metrics — per-model, per-provider request tracking
- Virtual models — define aliases like
fastorsmartthat map to multiple provider endpoints with routing strategies
Links
How is this guide?
Last updated on