Cohere

•

Open weights model

•

Released March 2025

Command A API Provider Benchmarking & Analysis

Model Comparison

This analysis is intended to support you in choosing the best API provider of Command A for your use-case.

Fastest

Azure

41.8 t/s

Cohere

17.6 t/s

Output speed

Total 2 providers

Lowest Latency

Cohere

2.45 s

Azure

3.05 s

Time to first token

Total 2 providers

Lowest Price

Cohere

$3.25

Azure

$3.25

Blended price (per 1M tokens)

Total 2 providers

Command A is available through 2 API providers, each offering different performance characteristics and pricing. Below is a comparison of the key metrics across providers.

For output speed, the top providers are Azure (41.8 t/s) and Cohere (17.6 t/s).
For latency, Cohere (2.45s) and Azure (3.05s) offer the lowest time to first token.
For pricing, Cohere (3.25) and Azure (3.25) offer the lowest blended prices per 1M tokens.
Cohere offers both the lowest latency and best pricing, making it attractive for cost-conscious applications. Azure is the fastest option for throughput-intensive workloads.

Speed

Output tokens per second · Higher is better

Latency

Seconds to first answer token received · Lower is better

Price

USD per 1M tokens (blended) · Lower is better

Update: Default performance benchmarking workload has updated to 10k input tokens to better reflect production use cases. You can still select different workloads above.

Pricing

Pricing: Cache Hit, Input, and Output: Command A

Price (USD per M Tokens) · Lower is better · 10,000 input tokens

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Cost per Intelligence Index Task: Command A

Weighted average cost (USD) per Intelligence Index task · Segmented by token type · Lower is better

No data available

Weighted average cost per Intelligence Index task. Each evaluation’s cost is calculated from input, cache hit, cache write, reasoning, and answer token prices, divided by task count, and weighted by its Intelligence Index weight.

Output Speed vs. Price: Command A

Blended at 7:2:1 (cache-input-output) · Output speed: output tokens per second · USD per 1M tokens (blended)

Most attractive quadrant

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Speed

Measured by Output Speed (tokens per second)

Output Speed: Command A

Output speed: output tokens per second · 10,000 input tokens

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Figures represent performance of the model's first-party API or the median across providers where a first-party API is not available.

Time per Intelligence Index Task: Command A

Weighted average decode time (minutes) per Intelligence Index task · Excludes TTFT and overhead time · Lower is better

No data available

The weighted average time (seconds) per Artificial Analysis Intelligence Index task. This is calculated by dividing output tokens per task by output speed, weighted by the relative weights of each benchmark in the Intelligence Index.

Cost per Task vs. Time per Task: Command A

Weighted average cost (USD) per Intelligence Index task · Weighted average decode time (minutes) per Intelligence Index task

Most attractive quadrant

No data available

Latency

Measured by Time (seconds) to First Token

Time to First Token: Command A

Seconds to first token received · Lower is better · 10,000 input tokens

Time to first token received, in seconds, after API request sent. For reasoning models which share reasoning tokens, this will be the first reasoning token. For models which do not support streaming, this represents time to receive the completion.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

Cache Behaviour

Cache Hit Rate: Command A

Share of cacheable input tokens served from cache · Median of the last four weeks, updated Oct 26, 2026

The share of cacheable input tokens served from the provider's prompt cache, measured during multi-turn agentic coding sessions. We regularly measure each endpoint and report a representative rate based on recent measurements. Higher values mean more of the input is billed at the cheaper cache-hit price, where the provider offers one, which lowers the effective cost of agentic workloads. For further details, see our methodology page.

Cost per Task vs. Cache Hit Rate: Command A

Weighted average cost (USD) per Intelligence Index task · Cache hit rate: median of the last four weeks, updated Oct 26, 2026

Most attractive quadrant

No data available

End-to-End Response Time

Seconds to output 500 tokens, calculated based on time to first token, 'thinking' time for reasoning models, and output speed

End-to-End Response Time: Command A

Seconds to output 500 tokens, including reasoning model 'thinking' time · Lower is better · 10,000 input tokens

Seconds to receive a 500 token response. Key components:

Input time: Time to receive the first response token
Thinking time (only for reasoning models): Time reasoning models spend outputting tokens to reason prior to providing an answer. Amount of tokens based on the average reasoning tokens across a diverse set of 60 prompts (methodology details).
Answer time: Time to generate 500 output tokens, based on output speed

Key Comparison Metrics & API Features



Cohere	288k	Open	--	17	2.82	31.48	--
Microsoft Azure	256k	Open	--	40	2.99	15.38	--

Frequently Asked Questions

Common questions about Command A providers

Command A is available through 2 API providers: Cohere and Azure. Each provider offers different performance characteristics and pricing.

Command A is currently available through 2 API providers that we benchmark and track.

The fastest providers for Command A by output speed are Azure (41.8 t/s) and Cohere (17.6 t/s). Output speed measures how quickly tokens are generated after the model starts responding.

The providers with the lowest time to first token for Command A are Cohere (2.45s) and Azure (3.05s). Lower latency means faster initial response time.

The most affordable providers for Command A by blended price are Cohere ($3.25 per 1M tokens) and Azure ($3.25 per 1M tokens). Blended price uses a 7:2:1 cache hit/input/output token ratio.

The providers with the lowest input token pricing for Command A are Cohere ($2.50 per 1M input tokens) and Azure ($2.50 per 1M input tokens).

The providers with the lowest output token pricing for Command A are Cohere ($10.00 per 1M output tokens) and Azure ($10.00 per 1M output tokens).

Output speed for Command A varies significantly across providers. Azure is the fastest at 41.8 t/s, which is 2.4x faster than Cohere at 17.6 t/s.

All 2 providers of Command A support JSON mode for structured output.

All 2 providers of Command A support function calling (tool use).

The best provider for Command A depends on your priorities: Azure offers the highest output speed, Cohere has the lowest latency, and Cohere provides the most competitive pricing.

When choosing a provider for Command A, consider: output speed (for throughput-intensive tasks), latency (for interactive applications requiring quick first responses), pricing (for cost-sensitive workloads), and API features like JSON mode or function calling.

Yes, provider performance can vary over time due to infrastructure changes, load balancing, and updates. We continuously benchmark all providers and display historical performance trends in the "Over Time" charts.

For information about Command A's intelligence, capabilities, modalities, and how it compares to other models, see the model overview page. View model overview

Command A API Provider Benchmarking & Analysis

Fastest

Lowest Latency

Lowest Price

Speed

Latency

Price

Pricing

Pricing: Cache Hit, Input, and Output: Command A

Cache Hit

Cost per Intelligence Index Task: Command A

Cost per Intelligence Index Task

Output Speed vs. Price: Command A

Output Speed

Speed

Output Speed: Command A

Output Speed

Model Performance Representation

Time per Intelligence Index Task: Command A

Time per Intelligence Index Task

Cost per Task vs. Time per Task: Command A

Cost per Intelligence Index Task

Latency

Time to First Token: Command A

Latency (Time to First Token)

Median

Cache Behaviour

Cache Hit Rate: Command A

What Cache Hit Rate Shows

Cost per Task vs. Cache Hit Rate: Command A

Cost per Intelligence Index Task

End-to-End Response Time

End-to-End Response Time: Command A

End-to-End Response Time

Key Comparison Metrics & API Features

Frequently Asked Questions

Where can I access Command A?

How many API providers offer Command A?

Which provider is fastest for Command A?

Which provider has the lowest latency for Command A?

Which provider is cheapest for Command A?

Which provider has the lowest input price for Command A?

Which provider has the lowest output price for Command A?

How much does speed vary across Command A providers?

Which Command A providers support JSON mode?

Which Command A providers support function calling?

Which is the best provider for Command A?

How do I choose a provider for Command A?

Does provider performance for Command A change over time?

What are the overall capabilities of Command A?