Kimi
Moonshot AI
Moonshot and Kimi Coding are two separate providers in OpenClaw: different keys, different endpoints and different model naming. Treat them as independent integrations, not as two model variants under one API.
Two Separate Providers
Moonshot Kimi API
Model references use moonshot/<modelId>, such as moonshot/kimi-k2.5.
Kimi Coding
Model references use kimi-coding/<modelId>, and the keys or endpoints are not interchangeable with the Moonshot API.
Common Setup
Moonshot
openclaw onboard --auth-choice moonshot-api-key Kimi Coding
openclaw onboard --auth-choice kimi-code-api-key Default model snippet
{
env: { MOONSHOT_API_KEY: "sk-..." },
agents: {
defaults: {
model: { primary: "moonshot/kimi-k2.5" }
}
}
} Notes
Common K2-series models include kimi-k2.5 and kimi-k2-thinking.
If you deploy in mainland China, it can make sense to switch to the region-specific endpoint mentioned in the documentation.
Only add detailed provider metadata in models.providers when you actually need custom cost, context or other overrides.