Command A vs Sonar
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.
Command A comes from Cohere and Sonar from Perplexity. 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.
Sonar is the cheaper of the two on input tokens at $1.00 / 1M tokens.
| Specification | Command A | Sonar |
|---|---|---|
| Provider | Cohere | Perplexity |
| Model ID | command-a-03-2025 | sonar |
| Context window | 256K | 128K |
| Max output | 8K | — |
| Input price | $2.50 / 1M tokens | $1.00 / 1M tokens |
| Output price | $10.00 / 1M tokens | $1.00 / 1M tokens |
| Knowledge cutoff | — | — |
| Input types | text | text, image, file |
| Output types | text | text |
| Plan | All paid plans | All paid plans |
Which should you use?
Pick Command A when…
- You need the larger context window — 256K against 128K.
- You want longer single responses — up to 8K output tokens.
Pick Sonar when…
- Cost matters: input runs at $1.00 / 1M tokens versus $2.50 / 1M tokens.
- You need image and file input, which the other model does not accept.
Related comparisons
Try both on Clade
You do not have to choose. One Clade subscription gives you Command A, Sonar, and every other model on the platform.