command-r vs sonar-pro
command-r is 20.0× cheaper on input than sonar-pro.
| command-r | sonar-pro | |
|---|---|---|
| Input / 1M | $0.15 | $3.00 |
| Cached input / 1M | — | — |
| Output / 1M | $0.60 | $15.00 |
| Context window | 128K | 200K |
| Max output | 4K | 8K |
| Provider | Cohere | Perplexity |
| Vision | No | No |
| Tool calling | Yes | No |
| Token count | estimated | estimated |
Capability for the money
Independent measurement · Artificial Analysis · read 2026-08-11Not the same tier: sonar-pro leads command-r by 29.4 points on hard reasoning (GPQA Diamond), for 22.9× the price.
Coding
writing and fixing code
LiveCodeBenchsonar-pro +22.7
Hard reasoning
graduate-level science and multi-step analysis
GPQA Diamondsonar-pro +29.4
Averaged over the benchmarks both models sat, command-r returns 63.2 points of pass rate per dollar of blended price against 7.1 — the ratio that decides whether the dearer model earns its rate.
Each figure is a pass rate: the share of that test set the model answered correctly, measured by a third party rather than self-reported by the lab. Rows are different tests of different difficulty, so compare a model against the other model, not one row against the next. No published following instructions or tool use score for one of these models, so those lenses are omitted. And a benchmark is not your workload — it narrows the shortlist, it does not pick for you.
Which to pick
- Cheaper input: command-r
- Cheaper output: command-r
- Larger context: sonar-pro
- Better at coding: sonar-pro (4.8% vs 27.5% on LiveCodeBench)
- Better at hard reasoning: sonar-pro (28.4% vs 57.8% on GPQA Diamond)
List price is not production cost. Output length, cache hit rate, retries and task quality move the real number more than the headline rate does — price your own prompt on the token ledger before deciding.
Related comparisons
command-r detail · sonar-pro detail · All Cohere pricing · All comparisons