Directory · Model comparison
Devstral 2 vs Qwen3.6-Flash
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 | Devstral 2 | Qwen3.6-Flash |
|---|---|---|
| Input cost / 1M | $0.40 | $0.25 |
| Output cost / 1M | $2.00 | $1.50 |
| Context window | 256,000 tokens | 1,000,000 tokens |
| MMLU score | — | — |
Cost verdict
Enter monthly input and output volumes to see total cost savings.
Devstral 2
- Input: 1M × $0.40 = $0.40
- Output: 1M × $2.00 = $2.00
- Total
- $2.40
Qwen3.6-Flash
- Input: 1M × $0.25 = $0.25
- Output: 1M × $1.50 = $1.50
- Total
- $1.75
Total cost savings
$0.65
Qwen3.6-Flash saves $0.65 per month vs the other model at this volume.
Model routing savings
Uses this page's verified rates. Devstral 2 is the premium route (higher combined per-1M cost); Qwen3.6-Flash handles routine traffic.
All premium
Devstral 2
$120.00
100% of input and output on the premium route
Routed stack
80% → Qwen3.6-Flash
20% → Devstral 2
$94.00
- Routine slice
- $70.00
- Premium slice
- $24.00
Monthly savings
$26.00
21.7% lower
Rates pulled from this page's model database entries (devstral-2, qwen3-6-flash) — 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.