K3Nova
K3
Use for long-horizon coding, end-to-end knowledge work, and deep reasoning where context length and quality matter more than raw speed.
Kimi model choices
| Model or ID | Best use | Limit to check |
|---|---|---|
| kimi-k3 | API flagship model for long-horizon coding and knowledge work | Reasoning effort and up-to-1M context availability |
| k3 | Kimi Code K3 model ID | Plan entitlement and context setting |
| k3-256k | Kimi Code K3 model with 256k context | Video input and compacting when switching from longer context |
| kimi-k2.6 | Conversation, code generation, vision, video, and agent tasks | Lower context than K3 |
| kimi-for-coding | Kimi Code routine development and code completion | Use the exact model ID in third-party tools |
Plain answer
Kimi model names matter because product surfaces and API model IDs are not interchangeable. In Kimi Code, k3 and k3-256k refer to Kimi K3 choices, while kimi-for-coding and kimi-for-coding-highspeed refer to Kimi K2.7 Code choices.
For the Kimi API, kimi-k3 is the flagship long-context model and kimi-k2.6 is the flexible model for text, image, video, conversation, code generation, and agent tasks.
Decision checklist
Use this section to keep the next step practical before you touch accounts, files, infrastructure, or hardware.
| Check | Look for | Why it matters |
|---|---|---|
| Read the official source | Start with the model card, help center, docs, or official product page before trusting summaries. | Model names, limits, and prices change. |
| Name the path | Decide whether you need a hosted app, API call, local client, or full self-managed deployment. | Different paths have different costs and account boundaries. |
| Check the boundary | Keep login, payment, API keys, private files, and account settings on the official surface. | A public guide should help you choose, not handle sensitive actions. |
| Keep evidence | Save the source link, date, version, and practical next step that shaped your decision. | This makes later review easier for a team. |
How to read the facts
K3-256k
Use when your job fits inside 256k context and you want a K3 path that can reduce quota pressure.
K2.6 and K2.7 Code
Use these when you need flexible multimodal chat, routine coding, or high-speed code output depending on the client.
Quick scan cards
kimi-k3
API flagship model for long-horizon coding and knowledge work Reasoning effort and up-to-1M context availability
k3
Kimi Code K3 model ID Plan entitlement and context setting
k3-256k
Kimi Code K3 model with 256k context Video input and compacting when switching from longer context
kimi-k2.6
Conversation, code generation, vision, video, and agent tasks Lower context than K3
kimi-for-coding
Kimi Code routine development and code completion Use the exact model ID in third-party tools
FAQ
Is Kimi K3 the same as k3?
k3 is the Kimi Code model ID for Kimi K3. In the API, the model ID is kimi-k3.
When should I use k3-256k?
Use it when your coding session fits inside 256k context and you want to reduce consumption compared with 1M context.
Why did my model switch fail?
Check the exact model ID, plan entitlement, context setting, and whether the tool supports the requested reasoning effort.