Cohere rows preserve official pricing-page evidence, including null values where a model is listed by Cohere but no confirmed token price is exposed in the public source.
Choose a current Cohere model from the same pricing rows, enter input tokens, output tokens, and request volume, then review the estimated monthly API cost.
Start with realistic input tokens, output tokens, model choice, request volume, and any cached or discounted input when listed rules that apply. Then compare the estimate against current model pricing and budget limits before launch.
These records are published separately from token pricing and are excluded from token calculators and the model token-price comparison.
These models publish separate text-input, audio-output, and token-hour storage components. They remain visible here and in the Dataset, but are excluded from ordinary text-token calculators.
Open a model page for its verified source, workload examples, price history, lifecycle details, and nearby alternatives.
Null or unverified values are displayed as Not listed, never as zero.
| Model | Input | Output | Cached Input | Unit | Status |
|---|---|---|---|---|---|
Aya Expanse 32BModel ID: aya-expanse-32bProvider: CohereDisplayed pricing: StandardEvidence | Input · USD per 1M input tokens$0.500 | Output · USD per 1M output tokens$1.50 | Cached input · USD per 1M cached input tokensNot listed | USD per 1M tokens | latestactive |
Command R+ 08-2024Model ID: command-r-plus-08-2024Provider: CohereDisplayed pricing: StandardEvidence | Input · USD per 1M input tokens$2.50 | Output · USD per 1M output tokens$10.00 | Cached input · USD per 1M cached input tokensNot listed | USD per 1M tokens | latestactive |
Use these Cohere pricing rows as planning inputs: calculate your monthly API cost with realistic token counts, or compare this provider with other AI models before routing production traffic.
Cohere API pricing is the usage-based cost of running Cohere models through API requests. The practical estimate depends on the selected model, input tokens, output tokens, monthly request volume, retries, and any listed caching or discount rules.
Estimate one representative request first: input tokens, expected output tokens, selected Cohere models, request volume, retry rate, and cached or discounted input when listed assumptions when they are listed. Then multiply by monthly traffic.
Open the Cohere API cost calculatorUse the table on this page to compare available Cohere rows per 1M tokens. Not listed values stay visible as Not listed, so unknown prices are not accidentally treated as zero.
Compare total workflow cost, not only the cheapest input token price. Output length, quality, retries, context size, and fallback routing can change the real monthly API bill.
Compare Cohere with other providersUse cases are planning categories, not pricing promises. Estimate each workflow with its own token shape, expected answer length, quality requirement, and fallback behavior.
Cohere is often evaluated for retrieval-heavy products, reranking, search, and knowledge assistant workflows.
Teams may compare Cohere model routes for classification, summarization, extraction, and support automation.
Cohere pricing can be part of a multi-provider plan when teams want alternatives for search, RAG, or enterprise AI workloads.
Compare Cohere with OpenAI, Claude, Gemini, and Mistral by input price, output price, cached-input behavior, context needs, latency, quality, and cost per successful task. Always verify current provider pricing before launch or procurement decisions.
Model a normal, high, and worst-case month with expected requests, input tokens, output tokens, retries, and model routes before exposing a feature to real traffic.
Decide which app, workspace, customer tier, or internal team can spend against the provider budget. Review burn rate weekly during launches and pricing changes.
Shorten repeated instructions, cap output length, avoid sending full history when a summary works, and route routine tasks to lower-cost models when quality testing supports it.
The existing calculator route is linked directly without invented provider or model query parameters.
Pricing data is informational and may lag provider changes. Always verify final billing decisions against provider pricing pages, contracts, dashboards, and invoices.
Cohere API cost depends on the selected model, input tokens, output tokens, request volume, retries, and any cached or discounted input when listed or discount rules that apply. Use the pricing table and calculator with your own workload assumptions instead of relying on a single average price.
Estimate one request with input tokens, expected output tokens, model choice, and current per-1M-token pricing. Then multiply by requests per user, active users, days per month, retry rate, and fallback calls.
Cohere models are usually evaluated for workflows such as enterprise search and rag, text generation and classification, provider diversification. The best route depends on quality, latency, context size, output length, and monthly budget.
Cohere can be cheaper or more expensive depending on the exact model, prompt size, output length, cache eligibility, retry rate, and quality target. Compare total workflow cost across providers before switching production traffic.
Not listed means the current local pricing source does not expose a confirmed numeric value for that field. It is intentionally not treated as zero. Check the official Cohere pricing page and billing dashboard before launch.
Control spend by setting monthly budget limits, measuring input and output tokens separately, capping output length, reducing repeated context, reviewing retry cost, and comparing model routes before high-volume traffic grows.