// head_to_head
Command R (08-2024) vs MiniMax M3.1 Flash
Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.
Command R (08-2024) and MiniMax M3.1 Flash are priced within ~10% of each other.
Command R (08-2024) does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
cohere
Command R (08-2024)
- Blended / 1M
- $0.262
- Context
- 128K
- Released
- Aug 30, 2024
- Overall score
- Not evaluated
minimax
MiniMax M3.1 Flash
- Blended / 1M
- $0.262
- Context
- 1.0M
- Released
- Oct 19, 2026
- Overall score
- 66.9
Specs and pricing
| Metric | Command R (08-2024) | MiniMax M3.1 Flash |
|---|---|---|
| LiveBench overall Weighted mean of the seven LiveBench category scores, 0–100. Higher is better. | — | 66.9 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | — | $0.0015 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.262 | $0.262 |
| Input price / 1M | $0.150 | $0.150 |
| Output price / 1M | $0.600 | $0.600 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | — | $0.015 |
| Context window | 128K | 1.0Mwin |
| Max output tokens | 4K | 524Kwin |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Command R (08-2024) on top, MiniMax M3.1 Flash below, both out of 100.
What each one costs to run
Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.
| Workload | Command R (08-2024) | MiniMax M3.1 Flash |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $84.00/mo | $74.28/mo |
| RAG assistant 8K in / 600 out × 100K requests | $156.00/mo | $102.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $168.00/mo | $92.40/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $195.00/mo | $188.25/mo |
| Bulk classification 500 in / 20 out × 5M requests | $435.00/mo | $367.50/mo |
Which should you pick?
You need to fit large documents in one call
MiniMax M3.1 Flash
Wider context window — 1.0M against 128K.
Command R (08-2024) vs MiniMax M3.1 Flash FAQ
Which is better, Command R (08-2024) or MiniMax M3.1 Flash?
Command R (08-2024) and MiniMax M3.1 Flash are priced within ~10% of each other. Command R (08-2024) does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
Is Command R (08-2024) cheaper than MiniMax M3.1 Flash?
They cost about the same. Both land near $0.262 per million tokens on a 3:1 input:output blend, so price is unlikely to be the deciding factor between them.
Does Command R (08-2024) or MiniMax M3.1 Flash have a bigger context window?
MiniMax M3.1 Flash has the larger context window: 128K for Command R (08-2024) against 1.0M for MiniMax M3.1 Flash. Note that a window you can fill is not a window you should fill — retrieval quality usually degrades well before the limit, and you pay for every token you put in it.
Do Command R (08-2024) and MiniMax M3.1 Flash support prompt caching?
MiniMax M3.1 Flash publishes a cached-input rate of $0.015 per million tokens against a full input rate of $0.150. The catalogue lists no separate cached rate for Command R (08-2024), which means the provider does not price it separately here — not that caching is unavailable.
Related comparisons
How these numbers are produced
- Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
- Scores — LiveBench release 2026-10-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
- Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
- “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.
Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.