AllocateKimi K2.7 Code vs GLM 5.2
On provider list prices, Kimi K2.7 Code costs $0.95 per million input tokens against $1.40 for GLM 5.2: 1.5x apart. Output is $4 against $4.40 (1.1x). On Allocate both bill at list plus the 7% transaction fee.
Kimi K2.7 CodeG GLM 5.2Specifications 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 $2,540 a month on Kimi K2.7 Code and $3,220 on GLM 5.2 at list: a gap of $680, or 1.3x.
Choose Kimi K2.7 Code for
- The lower list price ($0.95 in / $4 out per M tokens)
Choose GLM 5.2 for
- Agents on open weights
- Code and structured outputs
- Fine-tuning toward an owned model
Common questions
Which is cheaper, Kimi K2.7 Code or GLM 5.2?
Kimi K2.7 Code, on this workload shape. At list prices it is $0.95/$4 per million tokens in and out against $1.40/$4.40 for GLM 5.2. Billed on Allocate: $1.02/$4.28 against $1.50/$4.71, 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.7 Code or GLM 5.2?
Both publish open weights (Kimi K2.7 Code: Not listed; GLM 5.2: 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.