Cohere Command R and R+: Dated 2024 Prices and 2025 Deprecations

The August 2024 refresh provides a dated price source

Cohere announced its August model refresh on 30 August 2024. The dated model IDs command-r-08-2024 and command-r-plus-08-2024 had official input/output rates of $0.15/$0.60 and $2.50/$10 per million tokens respectively. The current model pages repeat those numbers. This is stronger evidence of a historical introduction tariff than a mutable modern price grid. Nevertheless, no historical claim should imply every later private contract paid exactly the same amount.

Avoid the unsuffixed alias trap

In September 2025, Cohere announced deprecations affecting command-r-03-2024 and command-r-plus-04-2024, including their unsuffixed command-r and command-r-plus aliases. The company pointed to August 2024 variants and Command A as alternatives. If a code example sends an old alias, it must not be silently counted as the newer dated model. A pricing archive should store the full exact endpoint string to avoid a false migration history.

A practical one-million-token workload

Suppose a dated Command R batch uses 0.8 million input and 0.2 million output tokens. At the August 2024 rates, the token subtotal is 0.8×$0.15 + 0.2×$0.60 = $0.24. With Command R+ at its corresponding rates, the same hypothetical token counts would cost 0.8×$2.50 + 0.2×$10 = $4. These are list-price comparisons of the same token counts, not independent performance tests or claims that both models produce equally useful answers.

When the legacy rate stops being enough

A team moving historical retrieval-augmented generation jobs to newer models should profile output length, tool calls, chunk retrieval, safety behaviour and enterprise support, rather than selecting on the oldest per-token headline. Deprecation is a separate attribute from price: a rate can be historically documented even after the model no longer accepts calls. Use versioned migration records, preserve invoice months, and maintain review flags where a date-specific continuation tariff has not been independently verified.

Before choosing a paid tier

Obtain the billing quote for the exact Cohere product, account geography, tier, model or subscription, currency and commitment length. If the provider offers several kinds of meters, forecast each independently rather than summing quantities in incompatible units. The relevant captured meters here include input_tokens_per_1m, output_tokens_per_1m. Build a low, expected and high workload from your own request logs or editorial schedule; a pricing page is not a credible estimate of how many retries or approvals your team will need.

For governance, add an approval threshold for paid overages, reconcile invoices with metered activity, and schedule a quarterly or release-triggered source audit. The absence of an identified enterprise rate, promotional expiry or regional tax line is not evidence that the amount is zero. This guide does not represent a product trial, capability benchmark, procurement offer or warranty of uninterrupted access.

Historical availability and boundaries

Preserve the precise source version, checked date and any stated effective date before reusing these figures. A model launch announcement may confirm an introductory token rate without proving which private offers remain available; a mutable plan page can describe a later product state. If a source changes after this cutoff, publish a new snapshot instead of silently editing the historical record. Specialised product evaluations belong to the relevant AI 02–09 editorial teams, while this article documents the billing model and its limitations.