Cohere API Pricing Explained (2026): Real Costs, Hidden Charges, and How to Cut Them

Cohere is priced for retrieval workloads, and that is where its bills behave differently from everyone else’s. Generation is only one of three metered surfaces — embed and rerank are separate products with separate rates, and on a real RAG pipeline they routinely cost more than the chat calls everyone budgeted for.

This guide covers how Cohere meters your usage, the charges that do not appear in the estimate most teams write on a whiteboard, a formula you can run against your own traffic, and the five changes that reliably move the number.

On specific numbers: per-token rates move as providers adjust capacity and compete on price, so this guide deliberately teaches the cost model rather than quoting figures that go stale. Read current rates from Cohere dashboard (dashboard.cohere.com) and put them into the formula below.

How Cohere Bills You

Cohere charges per million tokens for generation, with separate rates for embed and rerank calls. Cohere meters three distinct call types: generation (per million input and output tokens), embeddings (per million tokens embedded), and rerank (per search unit). Most cost modelling for Cohere fails because it accounts for the first and quietly ignores the other two.

The practical consequence is that two teams sending identical request volumes can receive bills that differ by an order of magnitude, purely from model selection and token discipline. Volume is rarely the variable worth optimizing first.

📡

Recommended

Catch Spend Spikes the Hour They Start

Runaway retry loops show up as an error-rate and latency anomaly long before they show up on an invoice. Monitor the endpoint and the billing surprise stops being a surprise.

Try Better Stack Free →

The Cost Formula

Every per-token provider reduces to the same arithmetic. Fill in your own rates and your own measured token counts:

monthly cost =
    (requests/month x avg input tokens  / 1,000,000) x input rate
  + (requests/month x avg output tokens / 1,000,000) x output rate
  + any per-request or per-unit charges x requests/month

The two terms that matter are the ones people guess at. Do not guess — the API tells you. Log the usage object returned on every response and take the real averages from a sample of production traffic:

// Log real token usage instead of estimating prompt length
const res = await client.chat.completions.create(body);
const { prompt_tokens, completion_tokens } = res.usage;
metrics.record('cohere.tokens.input', prompt_tokens);
metrics.record('cohere.tokens.output', completion_tokens);

A hundred sampled requests will beat any estimate you can reason your way to, because retrieved context and generated output are almost always larger than developers expect.

What Teams Forget to Budget For

Rerank is billed per search unit, not per token

Rerank charges by the number of documents scored per query, so widening your candidate set from 25 to 100 quadruples that line item regardless of document length. Retrieve narrowly, then rerank.

Re-embedding a corpus is the classic budget spike

Embedding is cheap per token and expensive per corpus. A nightly job that re-embeds everything, or a model upgrade that forces a full re-index, is the single largest one-off charge most Cohere users ever see. Embed incrementally on write.

Trial keys are rate-limited, not just credit-limited

Cohere’s free trial keys are explicitly non-production: low rate limits and no commercial use. Load-testing on a trial key measures the trial key, not the paid tier.

Private and cloud-marketplace deployments price differently

Cohere is available through cloud marketplaces and as a private deployment, and those contracts do not carry the public per-token rates. If you are at that scale, the list price is a starting point rather than the answer.

Five Changes That Actually Cut the Bill

1. Cap max_tokens on every call

Output tokens are the more expensive half of almost every model’s rate card, and an uncapped generation limit means you are budgeting for the worst case on every single request. Setting a realistic ceiling is a one-line change with an immediate effect on the invoice.

2. Cache identical and near-identical prompts

Production traffic is far more repetitive than it feels. A cache keyed on the normalized prompt removes that traffic from your bill entirely — not reduces it, removes it. This is usually the largest single saving available.

3. Route by tier of work, not by habit

Classification, routing, extraction and summarization rarely need your flagship model. Sending them to the cheapest model that passes your evals, and reserving the expensive one for user-facing generation, routinely cuts spend by more than half.

4. Trim context before you trim models

Bloated system prompts and unbounded chat history are billed on every turn, forever. Truncating history and pruning retrieved chunks costs nothing in quality if you measure it, and it compounds across every request you will ever make.

5. Alert on spend rate, not on the monthly total

A monthly budget alert tells you about the incident after it has finished billing you. Track tokens per hour and request volume as operational metrics, and a runaway loop shows up in minutes instead of at the end of the cycle.

🔐

Recommended

Separate Keys, Separate Cost Centers

Splitting Cohere keys per environment is how you find out that staging is half your bill. Keep those keys managed and rotated instead of copied into env files.

Try 1Password Free →

The Cost of Cohere Downtime

Outages are a pricing problem too, and it is the one nobody models. When Cohere starts returning 5xx responses, one of two things happens: your retry logic hammers the endpoint and inflates request counts against whatever eventually succeeds, or your traffic fails over to a backup provider on a different rate card and stays there until somebody notices.

Both failure modes are measured in hours of unnoticed degradation. Knowing within a minute that the provider is down — rather than working out from a support ticket that it has been down since lunchtime — caps the damage on the reliability side and the billing side at the same time.

Cap retries. An unbounded retry loop against a failing provider is a bill with no ceiling.
Make failover explicit and temporary. Route overflow to a backup, then route it back — automatically, not when someone remembers.
Alert on error rate, not just availability. Partial degradation costs more than a clean outage because retries succeed just often enough to keep going.
Track spend per hour. A spike in tokens per hour is the earliest possible signal that something is wrong upstream. See Cohere API Rate Limits Explained for the quota side of the same problem.

Cheaper Alternatives to Price Against

Every serious cost exercise needs a second quote. These providers serve overlapping workloads, so they double as both a price check and a failover target when Cohere has an incident.

OpenAI

Competing embedding and chat models; the standard baseline for comparing embed cost per million tokens.

Check OpenAI status →

Mistral

Offers both embeddings and generation, useful as a second quote on retrieval pipelines.

Check Mistral status →

Groq

Very low per-token generation rates for the answer step once retrieval is handled elsewhere.

Check Groq status →

Comparing headline per-token rates across providers is misleading on its own: a cheaper model that needs two attempts to produce a usable answer is not cheaper. Compare cost per acceptedoutput on your own evaluation set.

Frequently Asked Questions

How much does the Cohere API cost?

Cohere bills per million tokens for generation, with separate rates for embed and rerank calls. There is no single headline number, because your cost is a function of which model you call, how many tokens go in and out of each call, and how many calls you make. Rates change as capacity and competition shift, so read the current figures from Cohere dashboard (dashboard.cohere.com) and plug them into the cost formula in this guide rather than trusting any number quoted in a blog post — including this one.

Why is my Cohere bill higher than I estimated?

Three causes account for almost every surprise. First, output tokens are metered separately and usually cost more than input tokens, so an uncapped generation limit prices every request at its worst case. Second, retries and agent loops multiply request count invisibly. Third, the Cohere-specific factor most estimates miss: rerank is billed per search unit, not per token. Rerank charges by the number of documents scored per query, so widening your candidate set from 25 to 100 quadruples that line item regardless of document length.

Does Cohere have a free tier?

Cohere offers a free or trial allowance for evaluation, and it is sized for prototyping rather than production. Free tiers on every provider in this class carry tighter rate limits than paid ones, so a load test run against a free key measures the free key rather than the service. Check current allowances in Cohere dashboard (dashboard.cohere.com) before you size a plan around them.

How do I estimate Cohere costs before I ship?

Run a representative sample of real requests, log the token counts returned in each response, and multiply the averages by your projected request volume. Sampling one hundred real requests gives a far better forecast than reasoning about your prompt length, because retrieved context, system prompts and generated output are almost always larger than developers estimate.

Is a failed Cohere request still billed?

Generally no — a 429 or a 5xx that never produced a completion does not consume tokens. The cost of failure is indirect: aggressive retry loops turn one failed call into many successful expensive ones, and an outage you do not notice quickly can push a full day of traffic onto a pricier fallback provider. Monitoring the endpoint keeps both of those from becoming billing events.

Related Cohere Guides

Downtime Is a Line Item Too

API Status Check monitors Cohere and every other provider in your stack, so an outage never quietly reroutes a day of traffic onto a more expensive fallback.

Start Your Free Trial →

Cohere API Pricing Explained: Real Costs, Hidden Charges, and How to Cut Them