Granite Speech 5.0 TurboCTC vs Kimi K2 Thinking
At a Glance
| Compare | Kimi K2 ThinkingMoonshot AI | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.60Openrouter ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $2.50Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | Not reported | 262K |
| Model facts checked | Sep 2, 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
Side-by-Side Facts
| Field | Granite Speech 5.0 TurboCTC | Kimi-K2-Thinking |
|---|---|---|
| Developer | IBM | Moonshot AI |
| Family | Granite Speech 5 0 | Kimi K2 Thinking |
| Model | Granite Speech 5.0 TurboCTC | Kimi-K2-Thinking |
| Version | Granite Speech 5.0 TurboCTC | Kimi-K2-Thinking |
| Lifecycle | active | active |
| Released | 2026-08-25 | 2025-11-06 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Audio | Text |
| Output modalities | Text | Text |
| Context window | Unknown | 262K |
| Total parameters | 473M | 1T |
| Active parameters | Unknown | 32B |
| License | apache-2.0 | other |
| Open weights | Yes | Yes |
| API available | No | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Unknown | Hugging Face (Standard), Openrouter (Standard) |
| Capabilities | automatic-speech-recognition, transcription | chat, generation, reasoning, tools |
Granite Speech 5.0 TurboCTC Capabilities
Kimi K2 Thinking Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite Speech 5.0 TurboCTC vs Kimi K2 Thinking FAQs
Is Granite Speech 5.0 TurboCTC or Kimi K2 Thinking better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite Speech 5.0 TurboCTC and Kimi K2 Thinking, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
Only Kimi K2 Thinking has a directly sourced input price: $0.60 per million tokens. Only Kimi K2 Thinking has a directly sourced output price: $2.50 per million tokens.
Which has a larger context window, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
Neither model has a larger sourced context window in this comparison. Granite Speech 5.0 TurboCTC is — and Kimi K2 Thinking is 262K.
Which performs better in benchmarks, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Granite Speech 5.0 TurboCTC or Kimi K2 Thinking be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite Speech 5.0 TurboCTC is open weight; Kimi K2 Thinking is open weight.
Can Granite Speech 5.0 TurboCTC and Kimi K2 Thinking understand images?+
Granite Speech 5.0 TurboCTC is not documented with image input; Kimi K2 Thinking is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
Neither has a larger sourced maximum output. Granite Speech 5.0 TurboCTC is — and Kimi K2 Thinking is 131K.
Do Granite Speech 5.0 TurboCTC and Kimi K2 Thinking support reasoning and tool use?+
Granite Speech 5.0 TurboCTC: none of these features are definitively sourced. Kimi K2 Thinking: reasoning and tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
Granite Speech 5.0 TurboCTC has 0 sourced provider routes; Kimi K2 Thinking has 2, so Kimi K2 Thinking has broader tracked availability.
Which offers better value, Granite Speech 5.0 TurboCTC or Kimi K2 Thinking?+
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.