Side-by-side benchmark comparison across knowledge, coding, math, and reasoning.
Kimi K2.5 is clearly ahead on the aggregate, 68 to 43. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
Kimi K2.5's sharpest advantage is in mathematics, where it averages 76.8 against 26.4. The single biggest benchmark swing on the page is AIME 2024, 79 to 26.4. GPT-4.1 does hit back in knowledge, so the answer changes if that is the part of the workload you care about most.
GPT-4.1 is also the more expensive model on tokens at $2.00 input / $8.00 output per 1M tokens, versus $0.50 input / $2.80 output per 1M tokens for Kimi K2.5. That is roughly 2.9x on output cost alone. GPT-4.1 gives you the larger context window at 1M, compared with 128K for Kimi K2.5.
Pick Kimi K2.5 if you want the stronger benchmark profile. GPT-4.1 only becomes the better choice if knowledge is the priority or you need the larger 1M context window.
Kimi K2.5
64
GPT-4.1
78.3
Kimi K2.5
49.3
GPT-4.1
54.6
Kimi K2.5
76.8
GPT-4.1
26.4
Kimi K2.5
85
GPT-4.1
87.4
Kimi K2.5 is ahead overall, 68 to 43. The biggest single separator in this matchup is AIME 2024, where the scores are 79 and 26.4.
GPT-4.1 has the edge for knowledge tasks in this comparison, averaging 78.3 versus 64. Inside this category, MMLU is the benchmark that creates the most daylight between them.
GPT-4.1 has the edge for coding in this comparison, averaging 54.6 versus 49.3. Inside this category, SWE-bench Verified is the benchmark that creates the most daylight between them.
Kimi K2.5 has the edge for math in this comparison, averaging 76.8 versus 26.4. Inside this category, AIME 2024 is the benchmark that creates the most daylight between them.
GPT-4.1 has the edge for instruction following in this comparison, averaging 87.4 versus 85. Inside this category, IFEval is the benchmark that creates the most daylight between them.
Get notified when new models drop, benchmark scores change, or the leaderboard shifts. One email per week.
Free. No spam. Unsubscribe anytime. We only store derived location metadata for consent routing.