Kimi K2.7 Code vs GPT-5.6 Terra
At a Glance
| Compare |  Kimi K2.7 CodeMoonshot AI |  GPT-5.6 TerraOpenAI |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v2.5 | UnrankedNot in the 46-model eligible cohort | #13 of 4674.9 score · 3/3 sources · complete |
| CostLower is better · Published-token output estimate | #9 of 44$0.042 per LiveBench case | #35 of 44$0.266 per LiveBench case |
| EfficiencyHigher is better · MM Efficiency v1.5 | UnrankedNot in the 38-model eligible cohort | #23 of 3851.5 score · 3/3 sources · complete |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.68Deepinfra ↗ · Sep 22, 2026 | $2.00Openai ↗ · Sep 3, 2026 |
| Output priceFrom · USD / 1M tokens | $3.21Openrouter ↗ · Sep 22, 2026 | $12.00Openai ↗ · Sep 3, 2026 |
| Context windowMaximum documented tokens | 262K | 1,050K |
| Model facts checked | Sep 3, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
| Benchmark | Kimi K2.7 Code | GPT-5.6 Terra |
|---|---|---|
| LiveBench2026-06-25 · overall · leader | 71.4587% of row best · percent · kimi-k2.7-code · 13,007 output tokens / case | 82.31100% of row best · percent · gpt-5.6-terra-max · 22,145 output tokens / case |
| Overall ResultCounted from the protocol-matched rows above | 0 benchmark winsNo overall winner | 1 benchmark winNo overall winner |
Third-party benchmark Only like-for-like primary-publisher results are shown; raw scores, relative scores, configuration, and token spend remain visible.
Side-by-Side Facts
| Field | Kimi K2.7 Code | GPT-5.6 Terra |
|---|---|---|
| Developer | Moonshot AI | OpenAI |
| Family | Kimi K2 7 | Gpt 5 6 |
| Model | Kimi K2.7 Code | GPT-5.6 Terra |
| Version | Kimi K2.7 Code | GPT-5.6 Terra |
| Lifecycle | active | active |
| Released | 2026-06-11 | Unknown |
| Knowledge cutoff | Unknown | 2026-02-16 |
| Input modalities | Text, Image, Video | Text, Image |
| Output modalities | Text | Text |
| Context window | 262K | 1,050K |
| Total parameters | 1T | Unknown |
| Active parameters | 32B | Unknown |
| License | modified-mit | Unknown |
| Open weights | Yes | No |
| API available | Yes | Yes |
| Self-hostable | Yes | No |
| Provider access | Deepinfra (Standard), Fireworks Ai (Standard), Openrouter (Standard), Together Ai (Standard) | Openai (Standard), Openrouter (Standard) |
| Capabilities | agents, chat, coding, reasoning, tools, vision | chat, generation, reasoning, tools |
Kimi K2.7 Code Capabilities
GPT-5.6 Terra Capabilities
Related Comparisons
All image comparisons →| A | Pair | B | Context |
|---|---|---|---|
Kimi K2.7 CodeMoonshot AI | vs | GPT-6 AstraOpenAI | cross-developer peersimage, text |
Claude Fable 5.1Anthropic | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peersimage, text |
 Gemini 3.1 ProGoogle DeepMind | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peerstext |
 DeepSeek-V4.1-FlashDeepSeek | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peersimage, text |
Kimi K2.7 CodeMoonshot AI | vs | Grok 4.6xAI | cross-developer peersimage, text |
Kimi K2.7 CodeMoonshot AI | vs |  Qwen3.8-MaxQwen | cross-developer peersimage, text, video |
Kimi K2.7 CodeMoonshot AI | vs | Kimi-K3Moonshot AI | family variantsimage, text |
 MiniMax-M3MiniMax | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peersimage, text |
Kimi K2.7 CodeMoonshot AI | vs |  GLM-5.3Z.ai | cross-developer peerstext |
Kimi K2.7 CodeMoonshot AI | vs |  Hy4 previewTencent | cross-developer peerstext |
Seed 2.1 ProByteDance Seed | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peersimage, text, video |
 Mistral Large 3Mistral AI | vs | Kimi K2.7 CodeMoonshot AI | cross-developer peersimage, text |
Primary Evidence
Sources and Freshness
Questions
Kimi K2.7 Code vs GPT-5.6 Terra FAQs
Is Kimi K2.7 Code or GPT-5.6 Terra better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Kimi K2.7 Code and GPT-5.6 Terra, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Kimi K2.7 Code or GPT-5.6 Terra?+
Kimi K2.7 Code is $0.68 and GPT-5.6 Terra is $2.00 per million tokens, so Kimi K2.7 Code is cheaper on this metric. Kimi K2.7 Code is $3.21 and GPT-5.6 Terra is $12.00 per million tokens, so Kimi K2.7 Code is cheaper on this metric.
Which has a larger context window, Kimi K2.7 Code or GPT-5.6 Terra?+
GPT-5.6 Terra has the larger sourced context window. Kimi K2.7 Code supports 262K and GPT-5.6 Terra supports 1,050K.
Which performs better in benchmarks, Kimi K2.7 Code or GPT-5.6 Terra?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Kimi K2.7 Code or GPT-5.6 Terra be self-hosted?+
Kimi K2.7 Code is the only model in this pair currently marked as self-hostable. Kimi K2.7 Code is open weight; GPT-5.6 Terra is not marked open weight.
Can Kimi K2.7 Code and GPT-5.6 Terra understand images?+
Kimi K2.7 Code is documented with image input; GPT-5.6 Terra is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Kimi K2.7 Code or GPT-5.6 Terra?+
Neither has a larger sourced maximum output. Kimi K2.7 Code is — and GPT-5.6 Terra is 128K.
Do Kimi K2.7 Code and GPT-5.6 Terra support reasoning and tool use?+
Kimi K2.7 Code: reasoning, tool calling, and image input. GPT-5.6 Terra: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Kimi K2.7 Code or GPT-5.6 Terra?+
Kimi K2.7 Code has 4 sourced provider routes; GPT-5.6 Terra has 2, so Kimi K2.7 Code has broader tracked availability.
Which offers better value, Kimi K2.7 Code or GPT-5.6 Terra?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.