Get started
Configure an AI provider
Use Kition Cloud or connect OpenAI, Anthropic, DeepSeek, Kimi, or a supported custom endpoint.
Updated
By Kition Docs
Verified against Kition 0.1.41 (d3e1b931) on 2026-08-29
Choose how AI should run
- Kition Cloud — sign in with a Kition Account; no separate provider key is required
- OpenAI — Responses API with an OpenAI API key
- Anthropic — Messages API with an Anthropic API key
- DeepSeek — OpenAI-compatible Responses configuration
- Kimi — Moonshot OpenAI-compatible Responses configuration
- Custom — a supported Responses or Anthropic Messages endpoint with configurable authentication
Open AI Providers
Open Settings → AI Providers. Select a built-in provider or choose Add custom, then enter the connection values supplied by that provider.
After saving, use model sync to retrieve the available model list and choose the default model used by new Agents and chats.
Built-in defaults
- OpenAI base URL:
https://api.openai.com/v1; wire:responses - Anthropic base URL:
https://api.anthropic.com; wire:anthropic_messages - DeepSeek base URL:
https://api.deepseek.com/v1; wire:responses - Kimi base URL:
https://api.moonshot.cn/v1; wire:responses - Custom providers can set Base URL, models endpoint, auth header/scheme, and one of the two supported wire APIs
Wire compatibility
Kition 0.1.41 supports responses and anthropic_messages. Legacy Chat Completions is not a supported fallback. A service exposing only /chat/completions is not sufficient unless it also provides a compatible supported wire.
Heads up
Do not select a wire based only on the provider’s marketing name. Confirm that the endpoint implements the configured request and streaming behavior.
Credentials and model sync
- Use a project-scoped or limited provider key when the provider offers one
- Save the provider before syncing models
- Copy the model identifier returned by the provider rather than guessing from a display name
- Choose a default model after sync; switch per chat when a task needs another model
- Disconnect to disable a provider, then revoke or rotate its remote key; 0.1.41 does not reliably delete the saved local secret through this UI action
Common connection failures
401or403— invalid, expired, incomplete, or unauthorized credential404— incorrect Base URL, models path, wire, or model identifier429— provider request/token quota reached- No usable models — the models endpoint returned no compatible text-generation models
- Connection error — proxy, certificate, DNS, or local service availability problem
Implementation sources
Related pages
Protect provider credentials
Understand how Kition 0.1.41 stores provider secrets and reduce the impact of device or key compromise.
Set up OpenAI
Connect an OpenAI project key, sync the models available to that project, and use the Responses wire in Kition.
Set up Anthropic
Connect an Anthropic API key, sync the models available to its workspace, and use the Messages wire in Kition.
