Kimi CLI

Copy the configuration and replace sk-... with your key from the Ailoot Dashboard. Prefer storing the key in the environment variable AILOOT_API_KEY, if the application supports it.

Before starting, request GET /v1/models with your Ailoot key. Choose an exact model ID whose methods include POST /v1/chat/completions, POST /v1/responses, POST /v1/messages, POST /v1beta/models/{model}:generateContent, then use that ID in the configuration. For agents, also check tool support and the features required by your client version.

~/.kimi/config.toml

default_model = "ailoot-kimi"

[providers.ailoot]
type = "openai_legacy"
base_url = "https://api.ailoot.ai/v1"
api_key = "sk-..."

[providers.ailoot-claude]
type = "anthropic"
base_url = "https://api.ailoot.ai"
api_key = "sk-..."

[models.ailoot-kimi]
provider = "ailoot"
model = "kimi-k3"
max_context_size = 262144
capabilities = ["thinking"]

[models.ailoot-sonnet]
provider = "ailoot-claude"
model = "claude-sonnet-5-5"
max_context_size = 1000000
capabilities = ["thinking", "image_in"]

Example model: kimi-k3. Choose any other model from the catalog — check that it supports the format you need.

• For the OpenAI format, the URL is https://api.ailoot.ai/v1 (or the full path if the application asks for a full URL).
• For the Anthropic format, the URL is https://api.ailoot.ai without /v1.
• For the Gemini format, the URL is https://api.ailoot.ai — the API origin. The example above does not show the full setup for this format; consult the client’s documentation for the path to use in the relevant field. The API route prefix is /v1beta.
• Ask a short question. If you get an error, check the code and Request ID, then consult Errors and limits.
• 404 immediately after setup almost always means the URL is wrong: an extra or missing /v1.
• 402 — insufficient balance for the reserve. Agents reserve more than chat: why.

Application documentation: https://moonshotai.github.io/kimi-cli/en/configuration/providers.html