Command R+ vs Command A

Side-by-side API pricing comparison: which model gives you more for less?

Last verified Jun 2026 · Prices per 1M tokens

Cheaper Input
Command A
$2.5 vs $2.5
Cheaper Output
Command R+
$10 vs $10
Max Savings
0%
by switching to Command A
Save up to 0%
Switch from Command R+ to Command A · $2.5 input / $10 output per 1M tokens

Quick Comparison

FeatureCommand R+Command A
Provider Cohere Cohere
Tier Mid Mid
Input Price $2.5 $2.5
Output Price $10 $10
Context Window 128K 128K
Verified Jun 2026 Jun 2026

When to Use Each

💰 Cost-Sensitive Workloads

High-volume APIs, batch processing, and startups watching runway.

→ Use Command A — 0% cheaper input, 0% cheaper output

🧠 Complex Reasoning

Tasks requiring advanced reasoning, code generation, or nuanced analysis.

→ Either model works — compare quality on your specific tasks

⚡ High-Throughput APIs

Real-time chatbots, streaming responses, and latency-sensitive apps.

→ Command A for cost at scale, Command R+ if quality matters more

🔬 Prototyping & Testing

Development, experimentation, and non-critical workloads.

→ Use Command A — same context (128K), much cheaper

Track price changes for both models

APIpulse Pro monitors 49 models across 10 providers. Get alerts when Command R+ or Command A prices change.

Get Pro for $19 →

Frequently Asked Questions

Is Command A cheaper than Command R+?

Yes. Command A costs $2.5 input / $10 output per 1M tokens, while Command R+ costs $2.5 input / $10 output. That's 0% cheaper on input and 0% cheaper on output.

How much can I save switching to Command A?

For a typical workload (1M input + 500K output tokens/month), Command A costs $7.50/month vs $7.50/month for Command R+. That's a savings of $0.00/month (0%).

Which should I choose: Command R+ or Command A?

Choose Command A for cost efficiency. Choose Command R+ for Cohere ecosystem benefits. Both have 128K context windows.