Directory · Model comparison
DeepSeek-R1-0528 vs Kimi K2.7 Code
Side-by-side API economics and benchmarks. Per-1M input and output rates, context window, and verified metrics.
Tale of the tape
Head-to-head specs pulled from each model profile.
| Metric | DeepSeek-R1-0528 | Kimi K2.7 Code |
|---|---|---|
| Input cost / 1M | $0.50 | $0.95 |
| Output cost / 1M | $2.15 | $4.00 |
| Context window | 163,840 tokens | 262,144 tokens |
| MMLU score | — | — |
Cost verdict
Enter monthly input and output volumes to see total cost savings.
DeepSeek-R1-0528
- Input: 1M × $0.50 = $0.50
- Output: 1M × $2.15 = $2.15
- Total
- $2.65
Kimi K2.7 Code
- Input: 1M × $0.95 = $0.95
- Output: 1M × $4.00 = $4.00
- Total
- $4.95
Total cost savings
$2.30
DeepSeek-R1-0528 saves $2.30 per month vs the other model at this volume.
Model routing savings
Uses this page's verified rates. Kimi K2.7 Code is the premium route (higher combined per-1M cost); DeepSeek-R1-0528 handles routine traffic.
All premium
Kimi K2.7 Code
$247.50
100% of input and output on the premium route
Routed stack
80% → DeepSeek-R1-0528
20% → Kimi K2.7 Code
$155.50
- Routine slice
- $106.00
- Premium slice
- $49.50
Monthly savings
$92.00
37.2% lower
Rates pulled from this page's model database entries (kimi-k2-7-code, deepseek-r1) — same per-1M input/output figures as Tale of the tape. Production routing needs quality gates and monitoring.
Related comparisons
More head-to-head model matchups.