Skip to main content
BenchLM
Data

Mercury 2.5 vs MiniMax M2.7

Updated October 23, 2026. Rank says MiniMax M2.7 is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty.

Share or export
Share on XLinkedInAPI/MCP

Decision reading

MiniMax M2.7 has the higher public point estimate, 48.09 versus 33.38. Their conditional score ranges overlap. These ranges do not establish rank confidence. 3 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.

Model A
Inception logo

Inception

33.38/100

Estimated · Public rank #166

Conditional range 19.0–47.7

Model B
MiniMax logo

MiniMax

48.09/100

Supported · Public rank #108

90% interval 36.7–59.5

Shared results
3
Mercury 2.5 only
3
MiniMax M2.7 only
26
Like-for-like categories
2 / 8
Estimated: Mercury 2.5 · Supported: MiniMax M2.7. Conditional ranges do not establish rank confidence.How the comparison works

Which one for your work

Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.

  • Agentic work

    Tool use, computer use, and multi-step task completion

    MiniMax M2.7

    MiniMax M2.7 has the higher public agentic point estimate, 32.2 to 12, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

    Confidence: limited
  • Long documents

    Prompts that approach the documented context limit

    Mercury 2.5

    Mercury 2.5 has the larger documented context window.

    Confidence: documented
  • Chat turn cost

    1K fresh input + 500 output tokens

    Mercury 2.5

    Mercury 2.5 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.

    Confidence: listed-rates
Show secondary and unsupported calls
  • Repository review cost

    50K fresh input + 3K output tokens

    Mercury 2.5

    Mercury 2.5 has the lower estimated token cost for this stated workload. Costs use the listed standard API rates.

    Confidence: listed-rates
  • Coding work

    Code generation, repair, and software-engineering tasks

    Not enough matched evidence

    Mercury 2.5 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like.

    Confidence: limited
  • Cache-heavy agent loop cost

    200K cached + 20K fresh input + 10K output tokens

    Not enough matched evidence

    The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. MiniMax M2.7 does not fit this workload in one request. MiniMax M2.7 has no published cached-input rate, so cached tokens use its listed input rate.

    Confidence: rate-fallback

Which one for a specific job

Choose a job from the LLM Selector's task catalog to see the category row it rests on, under the same basis rules as the table below. A directional row stays directional; choosing a job never creates a winner.

The same task catalog as the LLM Selector. Each job names the evidence surface it rests on; nothing here adds a new score.

16.1Mercury 2.534.4MiniMax M2.7

Directional only · BenchAlign v5.8

MiniMax M2.7 has the higher coding point estimate. Conditional score ranges do not establish rank confidence.

Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.

Same basis rules as the category table below

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

2 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.

Shape of the matched evidence

Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.

A shared-evidence shape is not available.

BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.

Category results, on a stated basis

Each row shows the public-lane category score for both models: the BenchAlign v5.8 lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.

Agentic

Like-for-like
Mercury 2.5
12.0
Supported · #123/132
MiniMax M2.7
32.2
Supported · #94/132
Basis
BenchAlign v5.8 lane · 3 vs 8 public rows
Reading
MiniMax M2.7 leads

Knowledge

Like-for-like
Mercury 2.5
33.8
Supported · #139/187
MiniMax M2.7
45.4
Supported · #95/187
Basis
BenchAlign v5.8 lane · 1 vs 5 public rows
Reading
MiniMax M2.7 leads · intervals overlap

Coding

Directional only
Mercury 2.5
16.1
Estimated · #133/153
MiniMax M2.7
34.4
Supported · #82/153
Basis
BenchAlign v5.8 lane · 1 vs 12 public rows
Reading
Directional only

Instruction following

Directional only
Mercury 2.5
81.1
#60/153
MiniMax M2.7
93.0
#14/153
Basis
Provisional lane · 1 vs 0 weighted rows
Reading
Directional only

Reasoning

Not comparable
Mercury 2.5
71.7
Unranked · 2 rankable rows
MiniMax M2.7
78.8
Unranked · 2 rankable rows
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multimodal

Not comparable
Mercury 2.5
Not ranked
MiniMax M2.7
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multilingual

Not comparable
Mercury 2.5
Not ranked
MiniMax M2.7
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Math

Not comparable
Mercury 2.5
Not ranked
MiniMax M2.7
70.5
Unranked · 4 rankable rows
Basis
Provisional lane · 0 vs 2 weighted rows
Reading
Not comparable

Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign v5.8) differ from the provisional-lane categories. Unranked scores sit on the provisional lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.

Supported evidence per lane · bars run 0–100Methodology

What each workload costs

Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.

Chat turn

1K fresh input + 500 output tokens

Mercury 2.5
$0.00012
Fits in one request
MiniMax M2.7
$0.0009
Fits in one request

Mercury 2.5 has the lower modeled cost

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

Mercury 2.5
$0.00245
Fits in one request
MiniMax M2.7
$0.0186
Fits in one request

Mercury 2.5 has the lower modeled cost

Costs use the listed standard API rates.

Cache-heavy agent loop

200K cached + 20K fresh input + 10K output tokens

Mercury 2.5
$0.0031
Fits in one request
MiniMax M2.7
$0.078
Does not fit in one request
Cached input priced at the published list-input rate

MiniMax M2.7 does not fit this workload in one request. MiniMax M2.7 has no published cached-input rate, so cached tokens use its listed input rate.

Cached input falls back to the list input rate only where a cached rate is unpublished

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Documented inputs

Mercury 2.5

Not sourced

MiniMax M2.7

Not sourced

Documented outputs

Mercury 2.5

Not sourced

MiniMax M2.7

Not sourced

Provider availability

Mercury 2.5

Not sourced

MiniMax M2.7

Not sourced

Reasoning profile

Mercury 2.5

Reasoning

MiniMax M2.7

Non-Reasoning

Weight access

Mercury 2.5

Proprietary

MiniMax M2.7

Open Weight

License

Mercury 2.5

Proprietary

MiniMax M2.7

Open Weight

Release date

Mercury 2.5

2026-09-08

MiniMax M2.7

2026-03-18

If you already use one of these models

Deployment change
The models list different providers, so authentication, endpoint behavior, limits, and feature support may change.
Quality signal
MiniMax M2.7 has the higher public point estimate, 48.09 versus 33.38. Their conditional score ranges overlap. These ranges do not establish rank confidence.
Workload cost
Repository review: $0.00245 vs $0.0186. Cache-heavy agent loop: $0.0031 vs $0.078.
Context tradeoff
Mercury 2.5 has the larger documented window (260K).
Run the same representative tasks against both endpoints before changing production traffic.

Questions

Which is better, Mercury 2.5 or MiniMax M2.7?

MiniMax M2.7 has the higher public point estimate, 48.09 versus 33.38. Their conditional score ranges overlap. These ranges do not establish rank confidence. The page therefore keeps the decision tied to the specific documented workload.

Which is better for coding, Mercury 2.5 or MiniMax M2.7?

MiniMax M2.7 scores higher for coding on the public lane, 34.4 to 16.1. Mercury 2.5 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like. BenchLM does not name a winner for coding from a directional reading; read the shared benchmark rows directly and test the models on the same task set.

Which is better for agentic tasks, Mercury 2.5 or MiniMax M2.7?

MiniMax M2.7 has the higher public agentic tasks point estimate, 32.2 to 12, with Supported evidence for both models. The conditional ranges do not establish rank confidence.

Which costs less, Mercury 2.5 or MiniMax M2.7?

For the stated presets, chat costs $0.00012 on Mercury 2.5 and $0.0009 on MiniMax M2.7; repository review costs $0.00245 and $0.0186; the cache-heavy agent loop costs $0.0031 and $0.078. MiniMax M2.7 does not fit this workload in one request. MiniMax M2.7 has no published cached-input rate, so cached tokens use its listed input rate.

Which has the larger context window, Mercury 2.5 or MiniMax M2.7?

Mercury 2.5 has the larger documented context window: 260K, compared with 200K.

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence32 rows

Agentic

  • τ³-bench results

    Mercury 2.596.0%
    Source
    MiniMax M2.767.6%
    Source

    Mercury 2.5 leads this result

  • DeepSearchQA

    Mercury 2.534.0%
    Source
    MiniMax M2.7—

    Not directly comparable

  • Terminal-Bench 2.1 (Vals)

    Mercury 2.534.5%
    Source
    MiniMax M2.748.7%
    Source

    MiniMax M2.7 leads this result

  • Terminal-Bench 2.0

    Mercury 2.5—
    MiniMax M2.757%
    Source

    Not directly comparable

  • Toolathlon

    Mercury 2.5—
    MiniMax M2.746.3%
    Source

    Not directly comparable

  • MLE-Bench Lite

    Mercury 2.5—
    MiniMax M2.766.6%
    Source

    Not directly comparable

  • MM-ClawBench

    Mercury 2.5—
    MiniMax M2.762.7%
    Source

    Not directly comparable

  • Claw-Eval

    Mercury 2.5—
    MiniMax M2.748.7%
    Source

    Not directly comparable

  • Gert Labs

    Mercury 2.5—
    MiniMax M2.740.40%
    Source

    Not directly comparable

Coding

  • SciCode

    Mercury 2.538%
    Source
    MiniMax M2.7—

    Not directly comparable

  • SWE-bench Verified*

    Mercury 2.5—
    MiniMax M2.775.4%
    Source

    Not directly comparable

  • SWE-bench Pro

    Mercury 2.5—
    MiniMax M2.756.2%
    Source

    Not directly comparable

  • SWE-Rebench

    Mercury 2.5—
    MiniMax M2.751.9%
    Source

    Not directly comparable

  • SWE Multilingual

    Mercury 2.5—
    MiniMax M2.776.5%
    Source

    Not directly comparable

  • Multi-SWE Bench

    Mercury 2.5—
    MiniMax M2.752.7%
    Source

    Not directly comparable

  • VIBE-Pro

    Mercury 2.5—
    MiniMax M2.755.6%
    Source

    Not directly comparable

  • NL2Repo

    Mercury 2.5—
    MiniMax M2.739.8%
    Source

    Not directly comparable

  • Terminal-Bench 2.0

    Mercury 2.5—
    MiniMax M2.757.0%
    Source

    Not directly comparable

  • Vibe Code Bench

    Mercury 2.5—
    MiniMax M2.727.04%
    Source

    Not directly comparable

  • React Native Evals

    Mercury 2.5—
    MiniMax M2.771.4%
    Source

    Not directly comparable

  • LiveCodeBench (Vals)

    Mercury 2.5—
    MiniMax M2.779.9%
    Source

    Not directly comparable

  • SWE-bench (Vals)

    Mercury 2.5—
    MiniMax M2.773.8%
    Source

    Not directly comparable

Knowledge

  • GPQA-D

    Mercury 2.579.0%
    Source
    MiniMax M2.787.0%
    Source

    MiniMax M2.7 leads this result

  • HLE

    Mercury 2.5—
    MiniMax M2.728%
    Source

    Not directly comparable

  • MMLU-Pro (Arcee)

    Mercury 2.5—
    MiniMax M2.780.8%
    Source

    Not directly comparable

  • GPQA Diamond (Vals)

    Mercury 2.5—
    MiniMax M2.786.6%
    Source

    Not directly comparable

  • MMLU-Pro (Vals)

    Mercury 2.5—
    MiniMax M2.780.4%
    Source

    Not directly comparable

Instruction following

  • IFBench

    Mercury 2.577%
    Source
    MiniMax M2.7—

    Not directly comparable

Math

  • AIME25 (Arcee)

    Mercury 2.5—
    MiniMax M2.780.0%
    Source

    Not directly comparable

  • AIME26

    Mercury 2.5—
    MiniMax M2.789.8%
    Source

    Not directly comparable

  • HMMT Nov 2025

    Mercury 2.5—
    MiniMax M2.781.0%
    Source

    Not directly comparable

  • HMMT Feb 2026

    Mercury 2.5—
    MiniMax M2.772.7%
    Source

    Not directly comparable

32 public results · 3 shared

Watch Mercury 2.5 vs MiniMax M2.7

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 5,600+ readers.

Last updated October 23, 2026