{T}
TokenMath.net
Updated 2026-09-22 11:16 UTC
Head-to-Head Specification Battle

Command R (08-2024) vs Command A

Side-by-side technical and economic comparison between Cohere's Command R (08-2024) and Cohere's Command A.

Endpoint Availability & Transition Notice

Command R (08-2024): Classified as a Legacy Reference model (Tracked Production / Legacy Family).

Core Technical & Pricing Comparison
MetricCommand R (08-2024)Command AAdvantage
Provider OrganizationCohereCohere
Standard Input / 1M$0.15$2.00Command R (08-2024) (93% lower)
Cached Input / 1M$0.015$0.20Command R (08-2024) lower
Output / 1M$0.60$8.00Command R (08-2024) lower
Context Window128k256kCommand A (256k)
Max Generation Tokens4.1k64kCommand A
Tokenizer FamilyCohere BPE (~256k vocabulary)Cohere Byte-Pair Encoding (256k vocabulary)

Interactive Side-by-Side Cost Simulator

Live Delta
Input Tokens / Req2,500
Output Tokens / Req800
Daily Requests10,000
Command R (08-2024)LOWER COST
$205.88 / month
$0.00069 / request
Command A
$2,745.00 / month
$0.00915 / request
Selecting Command R (08-2024) saves $2,539.13 / month (92.5% savings) over Command A.

When to Choose Command R (08-2024)

Opt for Command R (08-2024) when your engineering requirements prioritize Cohere's ecosystem, specific tokenizer efficiencies (Calibrated Cohere Tokenizer (±3%)), or when your expected prompt-to-completion ratios favor its $0.15/M input rate.

When to Choose Command A

Opt for Command A when looking for Cohere's tooling integration, specific context window depth (256k tokens), or when output generation volume favors its $8/M rate.