Model comparison · accepted catalogue facts 2026-09-23

MiniMax M2.7 vs MiniMax M3

MiniMax M3 has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from MiniMax M2.7; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

Editorial comparison: Modality and reasoning change; licence caution Inclusion does not recommend either model.

MiniMax M2.7

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1404.6

Balanced effective USD / 1M tokens · lower is better

$0.525/M

MiniMax M3

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1433.5

Balanced effective USD / 1M tokens · lower is better

$0.525/M

Compare · model decision

Choose two or three models

Inspect the differences, estimate your workload and keep the evidence. All standard catalogue models are available, including unrated ones.

Catalogue facts
2026-09-23

2 / 3 selected · 0 requirements
Open public comparison link
Public workload and requirements

These settings are included in the share link. The fixed-request scenario and private evaluation data below are excluded.

A ↔ B

MiniMax M3 has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from MiniMax M2.7; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

Estimated blend: 75% input, 25% output; 0% cached input. Base context tier. Prompt length selects the billing tier. An unlisted cache-read rate uses that tier’s full input rate in this blend; missing required input or output rates prevent an estimate. The fixed-request estimate below validates actual context and output limits and requires a published cache-read rate when cache hits are assumed.

What changes between these models

Quality first, then estimated price. LMArena scores are human-preference measurements, not a benchmark of your application. A missing score is unrated.

  • MiniMax M2.7 · Meets the stated model requirements
  • MiniMax M3 · Meets the stated model requirements
Material differences and unknown evidence. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA MiniMax M2.7B MiniMax M3
LMArena general score (Elo)1,404.61,433.5Δ vs A: +28.9 Elo
Score interval half-width (± Elo)3.584.19Δ vs A: +0.61 Elo
LMArena document score (Elo)Unknown1,434.8
Context window (tokens)204,8001,048,576Δ vs A: +843,776 tokens
Output limit (tokens)131,072512,000Δ vs A: +380,928 tokens
Input modalitiestexttext, image, video
Open weightsUnknownSupported
Recorded licenceUnknownminimax-community
Distinct sellers in the catalogue813Δ vs A: +5
Recorded retirement dateUnknownUnknown
10 shared measured facts
Shared measured facts. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA MiniMax M2.7B MiniMax M3
Benchmark reasoning effortdefaultdefault
Estimated effective USD / 1M tokens$0.525$0.525Δ vs A: 0 USD/M
Base input USD / 1M tokens$0.3$0.3Δ vs A: 0 USD/M
Base output USD / 1M tokens$1.2$1.2Δ vs A: 0 USD/M
Base cached-input USD / 1M tokens$0.06$0.06Δ vs A: 0 USD/M
Tool useSupportedSupportedΔ vs A: 0
ReasoningSupportedSupportedΔ vs A: 0
Model providerMiniMaxMiniMax
Serving precision differs across offersSupportedSupportedΔ vs A: 0
Retirement evidenceNone announced; not a guaranteeNone announced; not a guarantee

Provider counts and precision flags describe catalogue offers. They do not establish the precision, availability, region, tool behaviour or limits of your chosen endpoint. Open each model’s provider table before switching.

Complete price ladders and billing conditions

MiniMax M2.7

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.3$1.2$0.06

MiniMax M3

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.3$1.2$0.06
Migration preflight · compare each candidate with model A

Keeping MiniMax M2.7 is a valid decision. No pairwise comparison certifies a drop-in replacement.

MiniMax M2.7 → MiniMax M3

No known model-capability loss

  • Provider endpoint, serving precision, availability and task success need your own verification. Catalogue model capabilities do not certify an endpoint.
Check alternatives to MiniMax M2.7

Estimate a fixed request shape

Private to this tab unless you save locally or explicitly export private details. These are estimates, not observed invoices. Cross-model token counts and task success are assumptions.

0.1 extra attempts means 10 extra full attempts per 100 requests. Cache writes, tool charges, taxes and unlisted charges are excluded.

  • MiniMax M2.7Estimated total: $1.2 1,000 full attempts · base rates
  • MiniMax M3Estimated total: $1.2 1,000 full attempts · base rates
Prompt and output sensitivity · sampled scenarios

Every point recalculates the entire request shape. Tier-boundary samples include one token below, at and above each threshold. Ordering between samples is not guaranteed. Lowest known cost excludes unknown estimates and is not a replacement recommendation.

Vary input; hold output, requests, cache and retries fixed.
Input tokensMiniMax M2.7MiniMax M3Coverage
2,000$1.2Lowest known$1.2Lowest knownAll computed
4,096$1.8288Lowest known$1.8288Lowest knownAll computed
32,768$10.4304Lowest known$10.4304Lowest knownAll computed
131,072$39.9216Lowest known$39.9216Lowest knownAll computed
Vary output; hold input, requests, cache and retries fixed.
Output tokensMiniMax M2.7MiniMax M3
128$0.7536$0.7536
2,048$3.0576$3.0576
8,192$10.4304$10.4304

Bring your observed evaluation results

JSON is parsed locally. Prompts, filenames, individual responses and extra fields are not retained. Import only aggregate measurements for selected models. Task/version labels do not establish that two evaluations used the same dataset.

Expected format
[{"model":"provider/exact-model-id","task":"support-answer","version":"rubric-1","attempts":100,"successes":84,"costUsd":2.4,"latencyMs":950}]

Use the exact catalogue ID. Replace the example values with observed measurements. Omit costUsd or latencyMs when they are unknown. No public score is inferred from these observations.

Keep the decision and its evidence

A portable record retains selected facts, complete tier ladders, public requirements and the publication manifest. It also embeds the full permitted public catalogue to verify the input artifact checksum. Files are larger for this reason (up to 2 MB); local storage is limited to 12 records. Team review is local to this browser; there is no hosted collaboration.

Saving is opt-in and includes private review fields. Shared comparison links never include them. Version 1 Check references remain separate and are not overwritten or guessed into this format.

Saved local decisions · 0

No version 2 decision records are stored in this browser.

Questions this page answers

Is MiniMax M2.7 a better-and-cheaper replacement for MiniMax M3?

MiniMax M3 has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from MiniMax M2.7; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

What is included in this comparison?

Accepted model capabilities, context and output limits, complete price-tier ladders, independent LMArena measurements and missing evidence. Provider endpoint precision and application success still need verification.

Can I compare a different workload or keep a decision record?

Yes. Change the public workload, prompt length and requirements in the comparison workspace. Fixed-request scenarios, aggregate evaluations and review notes stay local unless explicitly exported.

Evidence & Ask