Set up Kimi Beta
2 min read
Kujira connects to Kimi with a key. You can use a Kimi Code plan or Kimi Platform's pay-per-token access; each option is a different connection type, with its own key and endpoint.
Before you start
Open Settings > Models > Kimi. You will see Kimi's list of connections. When you add one, the type is chosen at that moment and cannot be changed afterwards, so decide first which one matches your account. Do not use the keys interchangeably.
| Connection type | Purpose | Where to create the key |
|---|---|---|
| Subscription | Kimi Code plan. | Kimi Code Console |
| API key | Pay per token. | Kimi Platform |
Connect a Kimi Code plan
This option uses a key from your Kimi Code plan and the subscription endpoint proposed automatically by Kujira.
Activate a Kimi Code plan
Subscribe to the Kimi Code plan you need: Moderato, Allegretto, Allegro, or Vivace.
Create a key
Open the Kimi Code console, select Create API Key, give it a name, and copy it before closing the dialog.
Save it in Kujira
In Settings > Models > Kimi, select Add connection, give it a name that says which account it is, choose the Subscription type, and paste the key. Keep the suggested endpoint: it differs from the pay-per-token endpoint.
Use pay per token
For usage-based billing, create a key in Kimi Platform and use it to add an API key connection. That connection uses the pay-per-token endpoint the dashboard proposes.
Keys are not interchangeable
Kimi Code and Kimi Platform keys come from different consoles. If you use a key with the wrong connection type, the agent cannot authenticate or usage is billed differently than expected.
Several Kimi connections
You can hold the plan and pay-per-token at the same time, or two different accounts: they are separate connections and none is redundant. One of them is marked as the default, used by agents that pick no connection; the rest are pinned by name from each agent's configuration.
Activate an agent
In the agent's Configuration > Model, choose the Kimi connection it should use under Connection, or leave Inherit from the organization to use the default, and then select a Kimi model. If the agent is running, changing the connection restarts it on its own; changing the model requires restarting it.