K3Nova
Inspect configured Kimi Code providers
Start with the provider list before adding or changing credentials.
kimi provider list
kimi provider catalog list --filter kimi
kimi provider catalog list --filter openaiAPI key compatibility checklist
| Check | Pass condition | If it fails |
|---|---|---|
| Issuer | The key issuer supports the endpoint you configure | Get a key from the correct provider |
| Base URL | The endpoint matches the tool protocol | Do not reuse the key |
| Model ID | The exact model ID is supported | Switch to a listed model |
| Billing | Usage is charged to the intended account | Stop before running long tasks |
How to choose
Do not assume a Kilo Code key works in Kimi Code. API keys belong to a provider, endpoint, and permission model. Kimi Code has its own documented provider and model configuration rules, and official Kimi Code API setup uses Kimi Code Console, base URLs, and exact model IDs.
If Kilo Code is acting as a provider or aggregator, check whether it exposes an OpenAI-compatible or Anthropic-compatible endpoint that Kimi Code can be configured to call. If it does not, the key is not interchangeable.
Copyable commands
Do not paste a key into Kimi Code until the issuer, endpoint, protocol, and model ID match.
Test a temporary OpenAI-compatible provider
Use this only when the key issuer documents an OpenAI-compatible endpoint.
export KIMI_MODEL_NAME="<model-id>"
export KIMI_MODEL_API_KEY="<provider-api-key>"
export KIMI_MODEL_BASE_URL="<provider-base-url>"
export KIMI_MODEL_PROVIDER_TYPE="openai"
kimi -p "Reply only: PROVIDER_READY"Smoke-test the endpoint directly
This catches a bad base URL or key before a long coding session.
BASE_URL="<provider-base-url>"
PROVIDER_API_KEY="<provider-api-key>"
curl -s "$BASE_URL/models" -H "Authorization: Bearer $PROVIDER_API_KEY"Clear temporary model variables
Use this when you are done with the temporary provider test.
unset KIMI_MODEL_NAME KIMI_MODEL_API_KEY KIMI_MODEL_BASE_URL KIMI_MODEL_PROVIDER_TYPEAI handoff prompt and permissions
Copy this prompt into Kimi Code, K3Nova, or another AI agent. Keep approval manual for file writes, shell commands, account actions, and secrets.
Copyable AI prompt
Use this to give the agent the task and safety boundary in one message.
You are my AI agent for this task: check whether a Kilo Code API key can be used with Kimi Code without exposing the key or assuming provider compatibility.
Start by restating the goal and the permissions you need.
Use official docs or the files I provide before making claims.
Give me a direct answer first, then a short table or checklist.
If commands are needed, show exact copyable commands without a shell prompt.
Ask before writing files, running shell commands, deleting or moving data, logging in, spending money, changing account settings, or handling API keys.
Stop and ask me when a step requires secrets, payment, account access, destructive cleanup, or a permission broader than the task.Recommended AI permissions
| Permission | Give AI | Why |
|---|---|---|
| Docs and config shape | Allow reading docs and non-secret config structure. | The agent can verify provider type, base URL shape, and model ID. |
| API keys | Do not show raw keys to the agent; paste secrets yourself into the approved config path. | Keys should not appear in chat, logs, or screenshots. |
| Config edits | Ask before Write or Edit to config.toml, mcp.json, shell profiles, or env files. | Credential changes need review. |
| Network tests | Ask before curl or model smoke tests, and keep prompts tiny. | Provider calls may bill the intended account. |
Test sequence
Identify the key issuer
Find who issued the key, what endpoint it authorizes, and which models it can call.
Check protocol compatibility
Kimi Code third-party setup documents OpenAI-compatible and Anthropic-compatible base URLs for Kimi Code API.
Do not paste keys blindly
A key that works in one tool can fail or leak if pasted into an unrelated provider field.
Test with a small request
After configuration, run a tiny model check before using the key in a long coding session.
Decision criteria
Provider keys are not names only
The same model family can appear behind different endpoints, auth headers, billing accounts, and rate limits.
Kimi Code exact IDs
Use documented IDs such as k3, k3-256k, kimi-for-coding, or kimi-for-coding-highspeed when configuring Kimi Code.
Credential storage
Kimi Code documents how configuration and credentials are stored. Follow that path rather than hardcoding keys in prompts or shell history.
FAQ
Can I paste a Kilo Code key into Kimi Code?
Only if the key's provider, endpoint, protocol, and model IDs are supported by the Kimi Code configuration you are using.
What is the safest test?
Run a small direct model request after configuration and confirm it bills the intended account.
Where should Kimi Code keys be configured?
Use the documented provider and model configuration path, not a chat prompt.