How to use Command A in production
A practical guide to command-a, using data from the AI & LLM Index. The goal is a shortlist and a decision, not a tour of every option.
What Command A is
Command A is a multimodal model from Cohere, released in 2025-05-09. Command A is a multimodal model from Cohere. It offers a 200,000-token context window, costs $13.30 per million input tokens and $67.41 per million output tokens, and averages 79.6 across the index's benchmark suite.
It is a proprietary model under a proprietary licence. That determines whether you can self-host it, fine-tune it and keep data inside your own infrastructure.
Pricing and context
Command A costs $13.30 per million input tokens, $67.41 per million output tokens and $1.13 per million cached input tokens. The blended 3:1 figure is about $26.83 per million tokens.
The context window is 200,000 tokens and the maximum output is 16,384 tokens. If your prompts regularly exceed the context window, you need chunking or retrieval before price becomes the main issue.
Benchmark position
Command A averages 79.6 across the index's scored benchmarks, ranking #132 of 600. Its strongest relative result is Arena Elo.
Use the table below to see the full benchmark profile. A single strong score is less useful than a consistent profile across the benchmarks that resemble your task.
Alternatives
The closest models by average score are Qwen3-Coder, Nova Pro Pro, Doubao 1.5 Pro. Compare their prices before assuming the closest score is the best substitute; a small quality drop can cut unit cost substantially.
Command A benchmark profile
| Benchmark | Score | Rank | Percentile |
|---|---|---|---|
| MMLU-Pro | 80.3 | #173 | 71th |
| GPQA Diamond | 74.2 | #161 | 73th |
| SWE-bench Verified | 70.6 | #99 | 84th |
| HumanEval | 83.1 | #159 | 74th |
| MATH-500 | 84.2 | #120 | 80th |
| AIME 2025 | 77.9 | #116 | 81th |
| LiveCodeBench | 71.8 | #150 | 75th |
| IFEval | 87.4 | #120 | 80th |
Related
FAQ
Is Command A worth it?
Command A averages 79.6 and costs $13.30 per million input tokens. Whether it is worth it depends on whether your task benefits from its benchmark profile; test it against a cheaper alternative.
What is the most important factor in command-a?
Fit to the task beats raw benchmark rank. Define the failure modes, pick the benchmarks that resemble them, then test a small shortlist on your own examples.
How many models should I evaluate?
Three is usually enough: a quality candidate, a value candidate and a fallback. More candidates add work without changing the decision.
How do I control cost?
Compare blended 3:1 price, watch output tokens, use caching where available and route simple requests to a cheaper model.