Moonshot AI (Kimi)

Moonshot provides the Kimi API with OpenAI-compatible endpoints. Configure the provider and set the default model to moonshot/kimi-k2.5, or use Kimi Coding with kimi/kimi-code.

Moonshot and Kimi Coding are separate providers. Keys are not interchangeable, endpoints differ, and model refs differ (moonshot/... vs kimi/...).

Built-in model catalog

Model ref	Name	Reasoning	Input	Context	Max output
`moonshot/kimi-k2.5`	Kimi K2.5	No	text, image	262,144	262,144
`moonshot/kimi-k2-thinking`	Kimi K2 Thinking	Yes	text	262,144	262,144
`moonshot/kimi-k2-thinking-turbo`	Kimi K2 Thinking Turbo	Yes	text	262,144	262,144
`moonshot/kimi-k2-turbo`	Kimi K2 Turbo	No	text	256,000	16,384

Getting started

Choose your provider and follow the setup steps.

Moonshot API
Kimi Coding

Best for: Kimi K2 models via the Moonshot Open Platform.

Choose your endpoint region

Auth choice	Endpoint	Region
`moonshot-api-key`	`https://api.moonshot.ai/v1`	International
`moonshot-api-key-cn`	`https://api.moonshot.cn/v1`	China

Run onboarding

velaclaw onboard --auth-choice moonshot-api-key

Or for the China endpoint:

velaclaw onboard --auth-choice moonshot-api-key-cn

Set a default model

{
  agents: {
    defaults: {
      model: { primary: "moonshot/kimi-k2.5" },
    },
  },
}

Verify models are available

velaclaw models list --provider moonshot

Config example

{
  env: { MOONSHOT_API_KEY: "sk-..." },
  agents: {
    defaults: {
      model: { primary: "moonshot/kimi-k2.5" },
      models: {
        // moonshot-kimi-k2-aliases:start
        "moonshot/kimi-k2.5": { alias: "Kimi K2.5" },
        "moonshot/kimi-k2-thinking": { alias: "Kimi K2 Thinking" },
        "moonshot/kimi-k2-thinking-turbo": { alias: "Kimi K2 Thinking Turbo" },
        "moonshot/kimi-k2-turbo": { alias: "Kimi K2 Turbo" },
        // moonshot-kimi-k2-aliases:end
      },
    },
  },
  models: {
    mode: "merge",
    providers: {
      moonshot: {
        baseUrl: "https://api.moonshot.ai/v1",
        apiKey: "${MOONSHOT_API_KEY}",
        api: "openai-completions",
        models: [
          // moonshot-kimi-k2-models:start
          {
            id: "kimi-k2.5",
            name: "Kimi K2.5",
            reasoning: false,
            input: ["text", "image"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 262144,
            maxTokens: 262144,
          },
          {
            id: "kimi-k2-thinking",
            name: "Kimi K2 Thinking",
            reasoning: true,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 262144,
            maxTokens: 262144,
          },
          {
            id: "kimi-k2-thinking-turbo",
            name: "Kimi K2 Thinking Turbo",
            reasoning: true,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 262144,
            maxTokens: 262144,
          },
          {
            id: "kimi-k2-turbo",
            name: "Kimi K2 Turbo",
            reasoning: false,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 256000,
            maxTokens: 16384,
          },
          // moonshot-kimi-k2-models:end
        ],
      },
    },
  },
}

Best for: code-focused tasks via the Kimi Coding endpoint.

Kimi Coding uses a different API key and provider prefix (kimi/...) than Moonshot (moonshot/...). Legacy model ref kimi/k2p5 remains accepted as a compatibility id.

Run onboarding

velaclaw onboard --auth-choice kimi-code-api-key

Set a default model

{
  agents: {
    defaults: {
      model: { primary: "kimi/kimi-code" },
    },
  },
}

Verify the model is available

velaclaw models list --provider kimi

Config example

{
  env: { KIMI_API_KEY: "sk-..." },
  agents: {
    defaults: {
      model: { primary: "kimi/kimi-code" },
      models: {
        "kimi/kimi-code": { alias: "Kimi" },
      },
    },
  },
}

Kimi web search

Velaclaw also ships Kimi as a web_search provider, backed by Moonshot web search.

Run interactive web search setup

velaclaw configure --section web

Choose Kimi in the web-search section to store plugins.entries.moonshot.config.webSearch.*.

Configure the web search region and model

Interactive setup prompts for:

Setting	Options
API region	`https://api.moonshot.ai/v1` (international) or `https://api.moonshot.cn/v1` (China)
Web search model	Defaults to `kimi-k2.5`

Config lives under plugins.entries.moonshot.config.webSearch:

{
  plugins: {
    entries: {
      moonshot: {
        config: {
          webSearch: {
            apiKey: "sk-...", // or use KIMI_API_KEY / MOONSHOT_API_KEY
            baseUrl: "https://api.moonshot.ai/v1",
            model: "kimi-k2.5",
          },
        },
      },
    },
  },
  tools: {
    web: {
      search: {
        provider: "kimi",
      },
    },
  },
}

Advanced

Native thinking mode

Moonshot Kimi supports binary native thinking:

thinking: { type: "enabled" }
thinking: { type: "disabled" }

Configure it per model via agents.defaults.models.<provider/model>.params:

{
  agents: {
    defaults: {
      models: {
        "moonshot/kimi-k2.5": {
          params: {
            thinking: { type: "disabled" },
          },
        },
      },
    },
  },
}

Velaclaw also maps runtime /think levels for Moonshot:

`/think` level	Moonshot behavior
`/think off`	`thinking.type=disabled`
Any non-off level	`thinking.type=enabled`

When Moonshot thinking is enabled, tool_choice must be auto or none. Velaclaw normalizes incompatible tool_choice values to auto for compatibility.

Streaming usage compatibility

Native Moonshot endpoints (https://api.moonshot.ai/v1 and https://api.moonshot.cn/v1) advertise streaming usage compatibility on the shared openai-completions transport. Velaclaw keys that off endpoint capabilities, so compatible custom provider ids targeting the same native Moonshot hosts inherit the same streaming-usage behavior.

Endpoint and model ref reference

Provider	Model ref prefix	Endpoint	Auth env var
Moonshot	`moonshot/`	`https://api.moonshot.ai/v1`	`MOONSHOT_API_KEY`
Moonshot CN	`moonshot/`	`https://api.moonshot.cn/v1`	`MOONSHOT_API_KEY`
Kimi Coding	`kimi/`	Kimi Coding endpoint	`KIMI_API_KEY`
Web search	N/A	Same as Moonshot API region	`KIMI_API_KEY` or `MOONSHOT_API_KEY`

Kimi web search uses KIMI_API_KEY or MOONSHOT_API_KEY, and defaults to https://api.moonshot.ai/v1 with model kimi-k2.5.
Override pricing and context metadata in models.providers if needed.
If Moonshot publishes different context limits for a model, adjust contextWindow accordingly.

Model selection

Choosing providers, model refs, and failover behavior.

Web search

Configuring web search providers including Kimi.

Configuration reference

Full config schema for providers, models, and plugins.

Moonshot Open Platform

Moonshot API key management and documentation.

Overview

Concepts and configuration

Providers

Moonshot AI

Moonshot AI (Kimi)

Built-in model catalog

Getting started

Config example

Config example

Kimi web search

Advanced

Model selection

Web search

Configuration reference

Moonshot Open Platform

​Moonshot AI (Kimi)

​Built-in model catalog

​Getting started

​Config example

​Config example

​Kimi web search

​Advanced

​Related

Model selection

Web search

Configuration reference

Moonshot Open Platform

Moonshot AI (Kimi)

Built-in model catalog

Getting started

Config example

Config example

Kimi web search

Advanced

Related