Sonar Pro vs Command A
Side-by-side specs, pricing and capabilities. Both models run on Clade under one subscription, so you can switch between them in the same conversation.
Sonar Pro comes from Perplexity and Command A from Cohere. The practical difference for most people is context, price, and which input types each one accepts.
Command A holds more in a single conversation — 256K tokens against 128K — which matters for long documents and large codebases.
Command A is the cheaper of the two on input tokens at $2.50 / 1M tokens.
| Specification | Sonar Pro | Command A |
|---|---|---|
| Provider | Perplexity | Cohere |
| Model ID | sonar-pro | command-a-03-2025 |
| Context window | 128K | 256K |
| Max output | — | 8K |
| Input price | $3.00 / 1M tokens | $2.50 / 1M tokens |
| Output price | $15.00 / 1M tokens | $10.00 / 1M tokens |
| Knowledge cutoff | — | — |
| Input types | text, image, file | text |
| Output types | text | text |
| Plan | Premium | Premium |
Which should you use?
Pick Sonar Pro when…
- You need image and file input, which the other model does not accept.
Pick Command A when…
- You need the larger context window — 256K against 128K.
- Cost matters: input runs at $2.50 / 1M tokens versus $3.00 / 1M tokens.
- You want longer single responses — up to 8K output tokens.
Related comparisons
Try both on Clade
You do not have to choose. One Clade subscription gives you Sonar Pro, Command A, and every other model on the platform.