Open-weight, coding-focused agentic model tuned for long-horizon software engineering with roughly 30% leaner reasoning-token usage.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Where Kimi K2.7 Code Earns Its Place: Long-Horizon Task Completion
Benchmarks
Reading Kimi K2.7 Code Benchmarks: Vendor-Reported Only
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Long-horizon autonomous coding agents
K2.7 Code is explicitly tuned to plan, edit across files, run tools, and debug over extended agent sessions. MoonshotAI reports higher end-to-end task success and more reliable long-context instruction following than K2.6. Because thinking is preserved across turns and reasoning tokens are ~30% leaner, cost per accepted change drops on runs spanning hundreds of steps. Ideal for repo-scale refactors and multi-file feature implementation. Validate with your own acceptance tests, since scores are vendor-reported.
MCP tool-use and CI loops
The model supports multi-turn function calling and scored 81.1 on MoonshotAI's MCP Mark Verified, which tests correct tool invocation via the Model Context Protocol. This fits agentic loops that run CI checks, update tickets, edit files, and fix failing migrations through MCP servers such as GitHub and Postgres in one session. Structured outputs and OpenAI/Anthropic-compatible APIs simplify wiring into existing agent harnesses.
High-volume, cost-sensitive coding at scale
For teams where output tokens dominate the bill, K2.7 Code benefits twice: roughly 30% fewer reasoning tokens per task, layered on lower per-token pricing than closed flagships. Long autonomous runs get cheaper at both the token-count and per-token level, making it well suited to high-throughput agentic coding where economics decide viability. Best when cost or data control is a priority over topping absolute benchmarks.
Self-hosted, data-residency-constrained deployments
Open weights under a Modified MIT License let privacy-sensitive organizations run K2.7 Code entirely in-house — on 8× H200-class hardware with vLLM, SGLang, or KTransformers — and drive it with Kimi Code CLI pointed at a local endpoint. This suits regulated codebases that cannot leave the perimeter, and enables fine-tuning a frontier-class coding model on proprietary code. Note the attribution clause applies at very large scale.