Cohere Provider Setup: Auth and Model Selection
Configure Cohere as a provider using the official OpenClaw plugin, set up API key authentication, and choose from the built-in model catalog. Useful for teams adding Cohere inference to an OpenAI-compatible stack.
Read this when
- You want to use Cohere with OpenClaw
- You need the Cohere API key env var or CLI auth choice
Cohere offers OpenAI-compatible inference via its Compatibility API. An official external plugin from OpenClaw makes Cohere available.
| Property | Value |
|---|---|
| Provider id | cohere |
| Plugin | @openclaw/cohere-provider |
| Auth env var | COHERE_API_KEY |
| Onboarding flag | --auth-choice cohere-api-key |
| Direct CLI flag | --cohere-api-key <key> |
| API | OpenAI-compatible (openai-completions) |
| Base URL | https://api.cohere.ai/compatibility/v1 |
| Default model | cohere/command-a-plus-05-2026 |
| Context window | 128,000 tokens |
Built-in catalog
| Model ref | Visibility | Input | Context | Max output | Notes |
|---|---|---|---|---|---|
cohere/command-a-plus-05-2026 | visible | text, image | 128,000 | 64,000 | Default; flagship agentic and reasoning model |
cohere/command-a-03-2025 | hidden | text | 256,000 | 8,000 | Previous generation; replaced by Command A+ |
cohere/command-a-reasoning-08-2025 | hidden | text | 256,000 | 32,000 | Previous generation; replaced by Command A+ |
cohere/command-a-vision-07-2025 | hidden | text, image | 128,000 | 8,000 | Previous generation; replaced by Command A+ |
cohere/north-mini-code-1-0 | visible | text | 256,000 | 64,000 | Agentic coding; reasoning; free limits |
Two reasoning modes are available through the Compatibility API for Cohere models that support reasoning. none is what OpenClaw uses for off, while any enabled thinking level maps to high. Because Command A Vision cannot use tools, OpenClaw leaves agent tools turned off for it.
Get started
- Add the official plugin:
openclaw plugins install @openclaw/cohere-provider
When a Gateway is running, the install is applied to it automatically; if not, it takes effect at the next startup. Refer to Apply changes and inspect.
- Generate a Cohere API key.
- Start onboarding:
openclaw onboard --non-interactive --accept-risk --skip-health \
--auth-choice cohere-api-key \
--cohere-api-key "$COHERE_API_KEY"
- Verify that the catalog is available:
openclaw models list --provider cohere
Cohere becomes the primary model through onboarding only if no primary model has been set already.
Your model entries survive onboarding, and generated catalog rows are left to discovery. In addition, with models.mode: "replace" the built-in catalog gets written, since that mode does not run discovery.
Environment-only setup
Expose COHERE_API_KEY to the Gateway process, then pick the Cohere model:
{
agents: {
defaults: {
model: { primary: "cohere/command-a-plus-05-2026" },
},
},
}
Note
For a Gateway that runs as a daemon or inside Docker, define
COHERE_API_KEYon that service. Setting it in an interactive shell alone will not reach a Gateway that is already running.