Kimi K2.6 vs Kimi K2.7 Code
Kimi K2.6 (Kimi) versus Kimi K2.7 Code (Kimi): API pricing, context window, capabilities and uptime, from the same data as each model page, at the WandAPI default channel price. Input costs 3.9 Credits / M for Kimi K2.6 and 3.9 Credits / M for Kimi K2.7 Code. Context windows are 256K and 256K.
Specs side by side
| Item | ||
|---|---|---|
| Input (prompt) · Credits / M | 3.9≈ $0.593 | 3.9≈ $0.593 |
| Output (completion) · Credits / M | 16.2≈ $2.46 | 16.2≈ $2.46 |
| Cache read · Credits / M | 0.66 | 0.06 |
| Context window | 256K | 256K |
| Max output | — | 256K |
| 7-day uptime | — | 94.2% |
| Latest probe latency | — | 2.0s |
| Measured throughput | 2.4 t/s | 187.5 t/s |
| Protocols | Anthropic Messages | Anthropic Messages |
| Sample monthly cost (10M in + 2M out) | 71.4≈ $10.85 | 71.4≈ $10.85 |
Prices are the WandAPI default channel price in Credits (1 Credit = ¥1); green marks the better side. Uptime and latency come from WandAPI probes; a dash means the model is not probed yet.
Capabilities
FAQ
Which has the larger context window, Kimi K2.6 or Kimi K2.7 Code?
Kimi K2.6 offers 256K tokens, Kimi K2.7 Code offers 256K tokens.
Can I switch between Kimi K2.6 and Kimi K2.7 Code at any time?
Yes. WandAPI calls every model with the same API key; switching is just changing the model field in the request, and billing is split per model in one console.
How do the capabilities of Kimi K2.6 and Kimi K2.7 Code differ?
Only Kimi K2.6: Vision, Video. Every other capability is either supported by both or by neither; see the capability table above.
More comparisons
One API key for both Kimi K2.6 and Kimi K2.7 Code
Free credits on sign-up, pay as you go, no monthly fee.