Kimi K2.5 vs Kimi K2.7 Code
On provider list prices, Kimi K2.5 costs $0.50 per million input tokens against $0.95 for Kimi K2.7 Code: 1.9x apart. Output is $2.80 against $4 (1.4x). On Allocate both bill at list plus the 7% transaction fee.
Specifications and provider list prices from the Allocate catalog, checked 2026-07-08. Billed price is list plus the 7% transaction fee.
What the numbers say
Take 1,000,000 requests a month at 1,200 input and 350 output tokens each. That workload costs $1,580 a month on Kimi K2.5 and $2,540 on Kimi K2.7 Code at list: a gap of $960, or 1.6x.
Choose Kimi K2.5 for
- Whole-document reasoning
- Long-context retrieval
- Open-weight fine-tuning
Common questions
Which is cheaper, Kimi K2.5 or Kimi K2.7 Code?
Kimi K2.5, on this workload shape. At list prices it is $0.50/$2.80 per million tokens in and out against $0.95/$4 for Kimi K2.7 Code. Billed on Allocate: $0.54/$3.00 against $1.02/$4.28, list plus 7%.
Which has the bigger context window?
They match: both read 262,144 tokens (256K) per request.
Can I fine-tune Kimi K2.5 or Kimi K2.7 Code?
Both publish open weights (Kimi K2.5: Not listed; Kimi K2.7 Code: Not listed), so both can be fine-tuned. On Allocate the trained weights stay inside your boundary and belong to you.
Related comparisons
Run the numbers on your workload
Or don’t choose. On Allocate a route name is the contract: point yours at one model today, swap to the other tomorrow, and compare them on your live traffic with per-token metering.