Compare
Kimi K2.5 vs Kimi K2p6
This page is context-first: how much text each model can take in one request. Full specs adds capabilities and limits; the pricing matrix below is only about $/million tokens from hosts that list both models.
Model
Kimi K2.5
Context window
262K
262,144 tokens · ~197K words
Model
Kimi K2p6
Context window
262K
262,144 tokens · ~197K words
Context window · side by side
Bar length is relative to the larger of the two windows (100% = max of this pair). This is not pricing.
Same context window size for both models.
Kimi K2.5 and Kimi K2p6 have identical context windows (262K tokens). Kimi K2.5 is 36% cheaper on input.
Quick verdicts
Short takeaways — validate with your own workloads.
RAG / high-volume retrieval
Use Kimi K2.5. Input tokens are 36% cheaper — critical when sending large retrieved contexts.
Full specs
Context, output, capabilities, and dates. Green highlights the favorable value where we compute a winner.
| Spec | Kimi K2.5 | Kimi K2p6 |
|---|---|---|
| Context window | 262,144 tokens (262K) | 262,144 tokens (262K) |
| Max output tokens | 262,144 tokens (262K) | 262,144 tokens (262K) |
| Speed tier | Balanced | Balanced |
| Vision | Yes | Yes |
| Function calling | Yes | Yes |
| Extended thinking | Yes | Yes |
| Prompt caching | Yes | Yes |
| Batch API | No | No |
| Release date | Jan 2026 | N/A |
Pricing matrix
Dollar rates only: hosts that list both models, per 1M tokens. For how much text fits, use the context section above — not this table.
| Provider | Kimi K2.5 in | Kimi K2.5 out | Kimi K2p6 in | Kimi K2p6 out |
|---|---|---|---|---|
| Azure | $0.600/M | $3.00/M | — | — |
| Baseten | $0.600/M | $3.00/M | — | — |
| Fireworks | — | — | $0.950/M | $4.00/M |
| Moonshot | $0.600/M | $3.00/M | — | — |
| Openrouter | $0.600/M | $3.00/M | — | — |
| Together Ai | $0.500/M | $2.80/M | — | — |
Frequently asked questions
Powered by Mem0
Use a smaller model.
Get better results.
Mem0 gives your AI long-term memory so you stop re-sending context on every call. That means you can use a smaller, faster, cheaper model — and still get better answers.
Example: a multi-turn chat session
80% less to send — works with any model