docs/providers/kilocode.md
Kilo Gateway routes requests to many models behind a single OpenAI-compatible endpoint and API key.
| Property | Value |
|---|---|
| Provider | kilocode |
| Auth | KILOCODE_API_KEY |
| API | OpenAI-compatible |
| Base URL | https://api.kilo.ai/api/gateway/ |
openclaw plugins install @openclaw/kilocode-provider
openclaw gateway restart
Or set the environment variable directly:
```bash
export KILOCODE_API_KEY="<your-kilocode-api-key>" # pragma: allowlist secret
```
The default model is kilocode/kilo/auto, a provider-owned smart-routing model. OpenClaw does not
publish a task-to-upstream-model mapping for it; routing behind kilo/auto is owned by Kilo Gateway.
At startup OpenClaw queries GET https://api.kilo.ai/api/gateway/models and merges discovered models
ahead of a static fallback catalog. The static fallback contains only kilocode/kilo/auto (Kilo Auto,
input: ["text", "image"], reasoning: true, contextWindow: 1000000, maxTokens: 128000).
Any model on the gateway is addressable as kilocode/<upstream-id> (for example
kilocode/anthropic/claude-sonnet-4, kilocode/openai/gpt-5.5). Run /models kilocode or
openclaw models list --provider kilocode to see the full discovered list.
{
env: { KILOCODE_API_KEY: "<your-kilocode-api-key>" }, // pragma: allowlist secret
agents: {
defaults: {
model: { primary: "kilocode/kilo/auto" },
},
},
}
- Gemini-backed Kilo refs stay on the proxy-Gemini path: OpenClaw sanitizes Gemini thought
signatures there but does not enable native Gemini replay validation or bootstrap rewrites.
- Requests use a Bearer token built from your API key.
<Warning>
`kilocode/kilo/auto` and `x-ai/*` refs skip reasoning-effort injection. Use a concrete model
ref such as `kilocode/anthropic/claude-sonnet-4` if you need reasoning support.
</Warning>