MiniMax · mit

MiniMax M2.5

MiniMax M2.5 by MiniMax appears in 1 source with Reasoning at 52.51. Best read for Code quality, Long context, Low cost.

CreatorMiniMax

Release date2026-02-12

Knowledge cutoffNot published

Context1M tokens

Input price$0.3/M tokens

Output price$1.2/M tokens

Modalitytext

CountryCN

Metrics

All source-backed metrics

Open in leaderboard

LLM Stats Rank42ranking · source_rank

Reasoning52.51reasoning · index_reasoning

Coding38.18coding · index_code

Research26.75research · index_search

Finance-1.02domain · index_finance

SWE-bench Verified80.2 %coding · swe_bench_verified_score

Code Arena1,060.74 %coding · coding_arena_score

BrowseComp76.3 %research · browsecomp_score

SWE-bench Pro55.4 %coding · swe_bench_pro_score

Context1,000,000 tokenscontext · context

Speed413.11 c/sperformance · throughput

Latency2,011.55 msperformance · latency

Input price0.3 $/Mpricing · input_price

Output price1.2 $/Mpricing · output_price

Parameters230,000,000,000 paramsmodel · params

Evidence

Citations and source overlap

LLM StatsPublic full LLM leaderboard advanced explorer snapshot, including ranking, benchmark indexes, pricing, speed, context, license, and model metadata.Retrieved 2026-06-01

FAQ

How should I read this profile?

Treat this as a source-backed model dossier, not an EvalKit-run verification. The public values are replicated from linked sources and kept source-scoped.

Is MiniMax M2.5 verified by EvalKit?

No. EvalKit currently shows 0 verified rows until real run evidence exists.

Why can metrics disagree?

Different sources test different tasks, dates, prompts, and aggregation methods. EvalKit keeps those differences visible instead of merging them into a fake universal score.