Granite 4.2 3B vs Kimi K2.7 Code
At a Glance
| Compare | Kimi K2.7 CodeMoonshot AI | |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| CostLower is better · Published-token output estimate | UnrankedNot in the 44-model eligible cohort | #9 of 44$0.042 per LiveBench case |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.030Deepinfra ↗ · Sep 21, 2026 | $0.68Deepinfra ↗ · Sep 21, 2026 |
| Output priceFrom · USD / 1M tokens | $0.12Deepinfra ↗ · Sep 21, 2026 | $3.21Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | 131K | 262K |
| Model facts checked | Sep 2, 2026View model evidence → | Sep 3, 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
Side-by-Side Facts
| Field | Granite 4.2 3B | Kimi K2.7 Code |
|---|---|---|
| Developer | IBM | Moonshot AI |
| Family | Granite 4 2 | Kimi K2 7 |
| Model | Granite 4.2 3B | Kimi K2.7 Code |
| Version | Granite 4.2 3B | Kimi K2.7 Code |
| Lifecycle | active | active |
| Released | 2026-08-25 | 2026-06-11 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text, Image, Video |
| Output modalities | Text | Text |
| Context window | 131K | 262K |
| Total parameters | 3.7B | 1T |
| Active parameters | Unknown | 32B |
| License | apache-2.0 | modified-mit |
| Open weights | Yes | Yes |
| API available | Yes | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Deepinfra (Standard) | Deepinfra (Standard), Fireworks Ai (Standard), Openrouter (Standard), Together Ai (Standard) |
| Capabilities | chat, generation, reasoning, structured_outputs, tools | agents, chat, coding, reasoning, tools, vision |
Granite 4.2 3B Capabilities
Kimi K2.7 Code Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite 4.2 3B vs Kimi K2.7 Code FAQs
Is Granite 4.2 3B or Kimi K2.7 Code better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite 4.2 3B and Kimi K2.7 Code, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Granite 4.2 3B or Kimi K2.7 Code?+
Granite 4.2 3B is $0.030 and Kimi K2.7 Code is $0.68 per million tokens, so Granite 4.2 3B is cheaper on this metric. Granite 4.2 3B is $0.12 and Kimi K2.7 Code is $3.21 per million tokens, so Granite 4.2 3B is cheaper on this metric.
Which has a larger context window, Granite 4.2 3B or Kimi K2.7 Code?+
Kimi K2.7 Code has the larger sourced context window. Granite 4.2 3B supports 131K and Kimi K2.7 Code supports 262K.
Which performs better in benchmarks, Granite 4.2 3B or Kimi K2.7 Code?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Granite 4.2 3B or Kimi K2.7 Code be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite 4.2 3B is open weight; Kimi K2.7 Code is open weight.
Can Granite 4.2 3B and Kimi K2.7 Code understand images?+
Granite 4.2 3B is not documented with image input; Kimi K2.7 Code is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Granite 4.2 3B or Kimi K2.7 Code?+
Neither has a larger sourced maximum output. Granite 4.2 3B is — and Kimi K2.7 Code is —.
Do Granite 4.2 3B and Kimi K2.7 Code support reasoning and tool use?+
Granite 4.2 3B: reasoning and tool calling. Kimi K2.7 Code: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Granite 4.2 3B or Kimi K2.7 Code?+
Granite 4.2 3B has 1 sourced provider route; Kimi K2.7 Code has 4, so Kimi K2.7 Code has broader tracked availability.
Which offers better value, Granite 4.2 3B or Kimi K2.7 Code?+
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.