Side-by-side comparison of pricing, 12 benchmarks, and generation speed.
| Metric | Command A+ | Mercury 2 |
|---|---|---|
| Input ($/M tokens) | $0 | $0.25 |
| Output ($/M tokens) | $0 | $0.75 |
Verdict. Command A+ and Mercury 2 split the benchmark comparison evenly at 1–1. The tiebreaker here is price, speed, and what you actually run them on.
Pricing. Pricing varies significantly between these models — check the table above for the exact per-token rates. Many production workloads actually surface input-token cost (retrieval-augmented prompts, code-context windows), so factor both directions.
Strengths. Command A+ is strongest on Coding Index (27.8), Intelligence Index (22.8). Mercury 2 leads on Coding Index (31.1), Intelligence Index (21.9).
Speed. On throughput, Mercury 2 generates tokens at 835 tok/s versus 207 tok/s — about 75% faster. On time-to-first-token, Command A+ responds in 380ms vs 3930ms, which matters most for chat-style UIs.
Provider. Cohere and Inception sell to overlapping but distinct developer audiences: Cohere tends to ship frontier reasoning models with premium positioning, while Inception often prices more aggressively. Your existing vendor relationships, billing, and SLA preferences may matter as much as the raw numbers above.
Workload cost. Workload scenarios (per million requests at 30M input + 15M output tokens): Command A+ costs $0.00 ($0/year); Mercury 2 costs $18.75 ($225/year). At a smaller 5M-input/2M-output scale (single-developer tool or prototype): Command A+ ≈ $0.00/run, Mercury 2 ≈ $2.75/run. At agent/realtime scale (200M input / 100M output per million requests): Command A+ ≈ $0/run, Mercury 2 ≈ $125/run. Command A+ becomes more attractive at higher volume — the absolute per-token pricing difference compounds when you ship at scale.
Recommendation. Both models have legitimate use cases — the right answer depends on whether you are optimizing for benchmark ceiling, latency, or unit cost. Start with the cheaper / faster model, evaluate against your specific task, and only switch if the upgrade shows a meaningful lift.
Head-to-head deltas
Data from Artificial Analysis API — 12 benchmarks
Command A+ is cheaper overall. Its blended price (3:1 input/output ratio) is $0.00/M tokens vs $0.38/M for Mercury 2.
It's a tie — both models win 1 benchmarks each across 12 evaluated categories. See the detailed benchmark chart above for per-category results.
Mercury 2 generates tokens faster at 835 tok/s vs 207 tok/s. Command A+ also has lower time-to-first-token (0.38s vs 3.93s).
Choose based on your priorities: Command A+ for lower cost, both perform similarly on benchmarks, and Mercury 2 for faster generation. For latency-sensitive apps, check the TTFT comparison above.