Skip to main content
ClawRouter gives OpenClaw one policy-scoped key for multiple upstream model providers. The bundled clawrouter plugin discovers only the models allowed for that key, routes each model through its declared protocol, and reports the key’s budget and aggregate usage on OpenClaw usage surfaces. Upstream credentials and provider-specific forwarding stay in ClawRouter, so you never install or authenticate each upstream provider plugin on the OpenClaw host. The plugin ships bundled with OpenClaw (enabledByDefault: true); you only need an issued ClawRouter credential.
PropertyValue
Providerclawrouter
Pluginbundled (included in OpenClaw)
AuthCLAWROUTER_API_KEY
Default URLhttps://clawrouter.openclaw.ai
Model catalogCredential-scoped via /v1/catalog
QuotasMonthly budget and usage via /v1/usage

​
Getting started

1

Get a scoped credential

Ask your ClawRouter administrator for a credential whose policy includes the providers, models, and monthly budget you should use. Credentials are revealed once when issued.
2

Configure OpenClaw

export CLAWROUTER_API_KEY="..."
openclaw onboard --auth-choice clawrouter-api-key
openclaw plugins enable clawrouter
clawrouter is bundled and enabled by default. If your configuration sets plugins.allow, add clawrouter to that list before enabling it. For a custom deployment, set models.providers.clawrouter.baseUrl to the ClawRouter origin; the default is https://clawrouter.openclaw.ai.
3

List granted models

openclaw models list --all --provider clawrouter
Use the returned model refs exactly as shown. They retain the upstream namespace, such as clawrouter/openai/gpt-5.5, clawrouter/anthropic/claude-sonnet-4-6, or clawrouter/google/gemini-3.5-flash. If agents.defaults.models is an allowlist in your configuration, add each selected ClawRouter ref to it.
4

Select a model

openclaw models set clawrouter/<provider>/<model>
You can also select a returned model for one run with openclaw agent --model clawrouter/<provider>/<model> --message "...".

​
Model discovery

GET /v1/catalog returns { providers: [...] }, where each provider entry lists its own models[] (with upstream id, capabilities, and pricing) and its supported request routes. OpenClaw does not ship a second, fixed list of ClawRouter models. A catalog model is advertised as an OpenClaw model when:
  • the credential’s policy grants its provider;
  • the catalog model advertises a supported LLM capability (llm.responses, llm.chat, llm.messages, or llm.stream with a matching streaming route); and
  • the provider exposes a matching route for one of the transports below.
Adding a model to a supported ClawRouter provider needs no OpenClaw release: the next catalog refresh (cached 60 seconds per credential scope) discovers it. A model that needs a new wire protocol requires plugin support first.

​
Protocol and provider plugins

ClawRouter owns upstream credentials; its catalog tells OpenClaw which transport to use, so you never install every upstream company’s auth plugin.
Catalog capability / routeOpenClaw transport
llm.responses (OpenAI-compatible provider)openai-responses
llm.chat (OpenAI-compatible provider)openai-completions
llm.messages + anthropic.messages routeanthropic-messages
llm.stream + streaming google.generate_content routegoogle-generative-ai
The plugin also applies the matching replay and tool-schema policies for those families (OpenAI/DeepSeek/Gemini tool-schema compat; native Anthropic and Google Gemini replay policies). A catalog provider exposing only an unsupported request format is intentionally not advertised as an OpenClaw text model. Normalize those providers to one of the supported contracts in ClawRouter rather than sending an incompatible payload.

​
Quotas and usage

ClawRouter’s /v1/usage response feeds the normal OpenClaw provider-usage surfaces: request, token, and spend totals, plus a monthly budget window when the key has a limit. Unmetered keys still show aggregate usage without a percentage window. Quota lookup uses the same scoped key as model discovery. A failed quota lookup does not block model execution. Check the live snapshot with: 
openclaw status --usage
openclaw models status
The same provider snapshot is available to /status in chat and OpenClaw’s usage UI. The budget is policy-wide, so requests made by another client using the same ClawRouter policy can change the remaining percentage.

​
Troubleshooting

SymptomCheck
No ClawRouter modelsConfirm the plugin is enabled and allowed by plugins.allow, then check that the credential is active and grants at least one ready provider.
A configured ClawRouter model is missingInspect its /v1/catalog capability and route support. Unsupported transport contracts are intentionally filtered.
Unknown model: clawrouter/...Add the exact catalog ref to agents.defaults.models when that configuration map is being used as an allowlist.
401 or 403 from catalog or usageReissue or re-scope the ClawRouter credential; OpenClaw does not fall back to upstream provider keys.
Model call fails after discoveryCheck the provider connection and upstream health in ClawRouter, then retry after its readiness state recovers.
Usage has totals but no percentageThe policy is unmetered; add a monthly budget in ClawRouter to expose a percentage window.

​
Security behavior

  • Catalog discovery is scoped to the configured proxy key and cached per credential scope (agent dir, workspace dir, auth profile id, and base URL).
  • The proxy key is attached only at request dispatch; it is not stored in model metadata.
  • Native Anthropic and Gemini model ids are rewritten to their upstream ids only at dispatch.
  • Unsupported or ungranted catalog rows fail closed and are not selectable.

Model providers

Provider configuration and model selection.

Usage tracking

OpenClaw usage and status surfaces.