Pick Command A for enterprise rag and retrieval or strong long-context retrieval accuracy. Pick MiniMax M3 for open-weight 428b moe (~23b active per token) with a 1m-token context or native multimodal input — text, image and video. Choose MiniMax M3 if you need self-hosting or data privacy; Command A if you want a managed API.
Command A (Cohere) and MiniMax M3 (MiniMax) are two of the models people most often weigh against each other in 2026. Command A is cohere's enterprise-focused model built for retrieval-augmented and grounded workloads. MiniMax M3 is miniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. They diverge most on price, context window and open vs. closed weights — each quantified below from the models' real specs.
Key differences
Price: MiniMax M3 is about 8.3× cheaper on input ($0.3/$1.2 per 1M tokens vs $2.5/$10 per 1M tokens) — a large enough gap that at scale it can be the single biggest line item in the decision.
Context window: MiniMax M3 holds 4.1× more — 1M (~1,573 pages) vs 256K (~384 pages). But effective recall usually fades long before the advertised ceiling, so the bigger number only helps if the model reasons over it.
Recency: MiniMax M3 is the newer model by about 15 months (released June 2026), usually meaning fresher training data and capabilities.
Specifications
Spec
Command A
MiniMax M3
Provider
Cohere (Global)
MiniMax (China)
Released
March 2025
June 2026
Context window
256K (~384 pages)
1M (~1,573 pages)
Price (in/out)
$2.5/$10 per 1M tokens
$0.3/$1.2 per 1M tokens
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, image, video, code
SWE-Bench Verified
Not published
Not published
MRCR v2 @ 1M
Not published
Not published
Who wins what
Enterprise RAG and retrieval: Command A — Command A lists enterprise RAG and retrieval among its strengths; MiniMax M3 does not.
Strong long-context retrieval accuracy: Command A — Command A lists strong long-context retrieval accuracy among its strengths; MiniMax M3 does not.
Multilingual: Command A — Command A lists multilingual among its strengths; MiniMax M3 does not.
Open-weight 428B MoE (~23B active per token) with a 1M-token context: MiniMax M3 — Its 1M window holds about 4.1× more than Command A's 256K in a single prompt.
Native multimodal input — text, image and video: MiniMax M3 — MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing — and it runs cheaper at $0.3/$1.2 per 1M tokens.
Reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5: MiniMax M3 — Open weights make this possible at all — Command A is API-only, so it cannot leave the vendor's servers.
Lowest cost at scale: MiniMax M3 — At $0.3/$1.2 per 1M tokens, it is the cheaper of the two — the gap dominates the bill on high-volume workloads.
Largest single-prompt input: MiniMax M3 — Its 1M window is about 4.1× larger than Command A's 256K, fitting roughly 1,573 pages in one prompt.
Which should you pick?
A cost-sensitive startup shipping high volume: MiniMax M3 — At $0.3/$1.2 per 1M tokens it undercuts Command A, and on millions of tokens that margin decides the monthly bill.
Someone analysing very long documents or codebases: MiniMax M3 — Larger 1M window fits more in one prompt.
A team with data-privacy or self-hosting needs: MiniMax M3 — Open weights let you run it on your own hardware; Command A is API-only.
Anyone whose priority is enterprise rag and retrieval: Command A — It is specifically built for that.
Anyone whose priority is open-weight 428b moe (~23b active per token) with a 1m-token context: MiniMax M3 — That is its strongest area.
Command A: where it fits
Cohere's enterprise-focused model built for retrieval-augmented and grounded workloads. Released March 2025 by Cohere, it is built for enterprise RAG and retrieval, strong long-context retrieval accuracy, multilingual, and tool use.
Its trade-offs are real: less consumer presence, and narrower modality support. At $2.5 in / $10 out per million tokens, it sits in the mid price band.
MiniMax M3: where it fits
MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. Released June 2026 by MiniMax, it is built for open-weight 428B MoE (~23B active per token) with a 1M-token context, native multimodal input — text, image and video, reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5, and low entry pricing at $0.30/$1.20 per million up to 512K tokens.
Its trade-offs: price doubles to $0.60/$2.40 above 512K tokens — not flat across 1M, miniMax's own reported 80.5 SWE-Bench Verified figure is vendor-stated, not independently verified, sWE-Bench Pro is a different, harder benchmark than SWE-Bench Verified, and newer than M2.7 but with less independent testing so far. At $0.3 in / $1.2 out per million tokens, it sits in the budget price band.
The bottom line for this matchup
The defining split here is open vs. closed. MiniMax M3 gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. Command A gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Frequently asked questions
Is Command A or MiniMax M3 better for coding?
Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, Command A leans toward enterprise rag and retrieval while MiniMax M3 leans toward open-weight 428b moe (~23b active per token) with a 1m-token context, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, Command A or MiniMax M3?
MiniMax M3 is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while Command A is API-metered at $2.5/$10 per 1M tokens. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
MiniMax M3 — 1M vs 256K, about 4.1× larger. Useful only if the model actually reasons over the full window, which not all do.
Can I use both Command A and MiniMax M3 together?
Yes — a multi-model platform like LumiChats gives you Command A, MiniMax M3 and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, Command A or MiniMax M3?
MiniMax M3 — released June 2026, about 15 months after Command A.
Command A vs MiniMax M3
Cohere · Global | MiniMax · China · Updated June 2026
Quick verdict
Pick Command A for enterprise rag and retrieval or strong long-context retrieval accuracy. Pick MiniMax M3 for open-weight 428b moe (~23b active per token) with a 1m-token context or native multimodal input — text, image and video. Choose MiniMax M3 if you need self-hosting or data privacy; Command A if you want a managed API.
Command A (Cohere) and MiniMax M3 (MiniMax) are two of the models people most often weigh against each other in 2026. Command A is cohere's enterprise-focused model built for retrieval-augmented and grounded workloads. MiniMax M3 is miniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. They diverge most on price, context window and open vs. closed weights — each quantified below from the models' real specs.
Key differences at a glance
▸Price: MiniMax M3 is about 8.3× cheaper on input ($0.3/$1.2 per 1M tokens vs $2.5/$10 per 1M tokens) — a large enough gap that at scale it can be the single biggest line item in the decision.
▸Context window: MiniMax M3 holds 4.1× more — 1M (~1,573 pages) vs 256K (~384 pages). But effective recall usually fades long before the advertised ceiling, so the bigger number only helps if the model reasons over it.
▸Recency: MiniMax M3 is the newer model by about 15 months (released June 2026), usually meaning fresher training data and capabilities.
Side-by-side specs
Spec
Command A
MiniMax M3
Provider
Cohere (Global)
MiniMax (China)
Released
March 2025
June 2026
Context window
256K (~384 pages)
1M (~1,573 pages)
Price (in/out)
$2.5/$10 per 1M tokens
$0.3/$1.2 per 1M tokens
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, image, video, code
SWE-Bench Verified
Not published
Not published
MRCR v2 @ 1M
Not published
Not published
Who wins what
Enterprise RAG and retrieval
Command A
Command A lists enterprise RAG and retrieval among its strengths; MiniMax M3 does not.
Strong long-context retrieval accuracy
Command A
Command A lists strong long-context retrieval accuracy among its strengths; MiniMax M3 does not.
Multilingual
Command A
Command A lists multilingual among its strengths; MiniMax M3 does not.
Open-weight 428B MoE (~23B active per token) with a 1M-token context
MiniMax M3
Its 1M window holds about 4.1× more than Command A's 256K in a single prompt.
Native multimodal input — text, image and video
MiniMax M3
MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing — and it runs cheaper at $0.3/$1.2 per 1M tokens.
Reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5
MiniMax M3
Open weights make this possible at all — Command A is API-only, so it cannot leave the vendor's servers.
Lowest cost at scale
MiniMax M3
At $0.3/$1.2 per 1M tokens, it is the cheaper of the two — the gap dominates the bill on high-volume workloads.
Largest single-prompt input
MiniMax M3
Its 1M window is about 4.1× larger than Command A's 256K, fitting roughly 1,573 pages in one prompt.
Which should you pick?
A cost-sensitive startup shipping high volume
→ MiniMax M3
At $0.3/$1.2 per 1M tokens it undercuts Command A, and on millions of tokens that margin decides the monthly bill.
Someone analysing very long documents or codebases
→ MiniMax M3
Larger 1M window fits more in one prompt.
A team with data-privacy or self-hosting needs
→ MiniMax M3
Open weights let you run it on your own hardware; Command A is API-only.
Anyone whose priority is enterprise rag and retrieval
→ Command A
It is specifically built for that.
Anyone whose priority is open-weight 428b moe (~23b active per token) with a 1m-token context
→ MiniMax M3
That is its strongest area.
Command A: where it fits
Cohere's enterprise-focused model built for retrieval-augmented and grounded workloads. Released March 2025 by Cohere, it is built for enterprise RAG and retrieval, strong long-context retrieval accuracy, multilingual, and tool use.
Its trade-offs are real: less consumer presence, and narrower modality support. At $2.5 in / $10 out per million tokens, it sits in the mid price band.
MiniMax M3: where it fits
MiniMax's open-weight 428B multimodal model with a 1M context — strong reported coding (59.0 SWE-Bench Pro) at low entry pricing. Released June 2026 by MiniMax, it is built for open-weight 428B MoE (~23B active per token) with a 1M-token context, native multimodal input — text, image and video, reports 59.0 on SWE-Bench Pro (a strong open-weight score), surpassing GPT-5.5, and low entry pricing at $0.30/$1.20 per million up to 512K tokens.
Its trade-offs: price doubles to $0.60/$2.40 above 512K tokens — not flat across 1M, miniMax's own reported 80.5 SWE-Bench Verified figure is vendor-stated, not independently verified, sWE-Bench Pro is a different, harder benchmark than SWE-Bench Verified, and newer than M2.7 but with less independent testing so far. At $0.3 in / $1.2 out per million tokens, it sits in the budget price band.
The bottom line for this matchup
The defining split here is open vs. closed. MiniMax M3 gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. Command A gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Want both Command A and MiniMax M3 without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.
Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, Command A leans toward enterprise rag and retrieval while MiniMax M3 leans toward open-weight 428b moe (~23b active per token) with a 1m-token context, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, Command A or MiniMax M3?
MiniMax M3 is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while Command A is API-metered at $2.5/$10 per 1M tokens. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
MiniMax M3 — 1M vs 256K, about 4.1× larger. Useful only if the model actually reasons over the full window, which not all do.
Can I use both Command A and MiniMax M3 together?
Yes — a multi-model platform like LumiChats gives you Command A, MiniMax M3 and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, Command A or MiniMax M3?
MiniMax M3 — released June 2026, about 15 months after Command A.
Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.