AllocateDeepseek V3.1 NVFP4 vs Kimi K2.7 Code
On provider list prices, Deepseek V3.1 NVFP4 costs $0.60 per million input tokens against $0.95 for Kimi K2.7 Code: 1.6x apart. Output is $1.70 against $4 (2.4x). On Allocate both bill at list plus the 7% transaction fee.
Deepseek V3.1 NVFP4
Kimi K2.7 CodeSpecifications 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,315 a month on Deepseek V3.1 NVFP4 and $2,540 on Kimi K2.7 Code at list: a gap of $1,225, or 1.9x.
Kimi K2.7 Code reads 256K tokens per request against 128K for Deepseek V3.1 NVFP4, 2.0x the window. That decides which one can take whole documents without splitting them.
Choose Deepseek V3.1 NVFP4 for
- The lower list price ($0.60 in / $1.70 out per M tokens)
- Fine-tuning under a permissive license (MIT)
Choose Kimi K2.7 Code for
- The longer context window (256K vs 128K tokens)
- Published cached-input pricing ($0.19 per M tokens)
Common questions
Which is cheaper, Deepseek V3.1 NVFP4 or Kimi K2.7 Code?
Deepseek V3.1 NVFP4, on this workload shape. At list prices it is $0.60/$1.70 per million tokens in and out against $0.95/$4 for Kimi K2.7 Code. Billed on Allocate: $0.64/$1.82 against $1.02/$4.28, list plus 7%.
Which has the bigger context window?
Kimi K2.7 Code: 262,144 tokens (256K) against 131,072 (128K) for Deepseek V3.1 NVFP4.
Can I fine-tune Deepseek V3.1 NVFP4 or Kimi K2.7 Code?
Both publish open weights (Deepseek V3.1 NVFP4: MIT; 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.