Granite Speech 5.0 TurboCTC NC vs Kimi K2 Instruct
At a Glance
| Compare | Kimi K2 InstructMoonshot AI | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.57Openrouter ↗ · Aug 29, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $2.30Openrouter ↗ · Aug 29, 2026 |
| Context windowMaximum documented tokens | Not reported | 131K |
| 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 NC | Kimi-K2-Instruct |
|---|---|---|
| Developer | IBM | Moonshot AI |
| Family | Granite Speech 5 0 | Kimi K2 Instruct |
| Model | Granite Speech 5.0 TurboCTC NC | Kimi-K2-Instruct |
| Version | Granite Speech 5.0 TurboCTC NC | Kimi-K2-Instruct |
| Lifecycle | active | active |
| Released | 2026-08-25 | 2025-07-11 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Audio | Text |
| Output modalities | Text | Text |
| Context window | Unknown | 131K |
| Total parameters | 473M | 1T |
| Active parameters | Unknown | 32B |
| License | cc-by-nc-sa-4.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, tools |
Granite Speech 5.0 TurboCTC NC Capabilities
Kimi K2 Instruct Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite Speech 5.0 TurboCTC NC vs Kimi K2 Instruct FAQs
Is Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite Speech 5.0 TurboCTC NC and Kimi K2 Instruct, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
Only Kimi K2 Instruct has a directly sourced input price: $0.57 per million tokens. Only Kimi K2 Instruct has a directly sourced output price: $2.30 per million tokens.
Which has a larger context window, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
Neither model has a larger sourced context window in this comparison. Granite Speech 5.0 TurboCTC NC is — and Kimi K2 Instruct is 131K.
Which performs better in benchmarks, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
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 NC or Kimi K2 Instruct be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite Speech 5.0 TurboCTC NC is open weight; Kimi K2 Instruct is open weight.
Can Granite Speech 5.0 TurboCTC NC and Kimi K2 Instruct understand images?+
Granite Speech 5.0 TurboCTC NC is not documented with image input; Kimi K2 Instruct is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
Neither has a larger sourced maximum output. Granite Speech 5.0 TurboCTC NC is — and Kimi K2 Instruct is —.
Do Granite Speech 5.0 TurboCTC NC and Kimi K2 Instruct support reasoning and tool use?+
Granite Speech 5.0 TurboCTC NC: none of these features are definitively sourced. Kimi K2 Instruct: tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
Granite Speech 5.0 TurboCTC NC has 0 sourced provider routes; Kimi K2 Instruct has 2, so Kimi K2 Instruct has broader tracked availability.
Which offers better value, Granite Speech 5.0 TurboCTC NC or Kimi K2 Instruct?+
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.