Flint vs MiMo-V2.6-Flash

Overall
21
vs
Overall
45

MiMo-V2.6-Flash is clearly better. It wins 45 of the 48 test cases where they differ.

Learn to build evals like this in the AI Engineering Academy

Task by task

A score turns orange only when that model wins clearly more of the task's test cases. Under each score, the average time per test case on the machine it ran on. Flint spends 2.5× as many thinking tokens per test case.

Thinking tokensAnswer tokens
TaskAB
Overall
211m 17s
10.9K, 90% thinking4.2K, 92% thinking
451m 21s
Agents
1447.7s
4.8K, 85% thinking2.2K, 86% thinking
381m 19s
Structured Extraction
291m 17s
10.9K, 87% thinking2.6K, 91% thinking
6238.0s
Coding
141m 19s
12K, 98% thinking9.9K, 97% thinking
242m 40s
Grounded Answers
2957.7s
8.7K, 93% thinking2.6K, 89% thinking
6242.1s
Instruction Following
352m 28s
22.2K, 93% thinking4.8K, 90% thinking
641m 2s
Business Logic
101m 20s
11.7K, 78% thinking4.4K, 96% thinking
4356.4s
Security & permissions
3552.6s
7.1K, 90% thinking3.8K, 88% thinking
662m 6s
Diagnosis & investigation
057.0s
7.3K, 99% thinking1.5K, 83% thinking
01m 33s

What you'd run

The build behind each score. Orange marks the faster, smaller, cheaper or longer-context side.

SpecAB
Speed
149 tok/s (better)
66 tok/s
Machine
Hosted
Hosted
Memory at 32K
—
—
Context
256K
1.1M (better)
Cost per run
Not measured
$0.33
Cost per case
Not measured
$0.0021
Time per case
1m 17s (better)
1m 21s
Quantization
BF16
BF16
Harness
openrouter
openrouter

The race

No lead changes

Each model's running score as the test cases go by. The dashed line is a perfect run.

FlintMiMo-V2.6-Flash
0255075100501001502145

Every test case

153 test cases

Each square is one test case, colored by the model that scored higher.

3 won by Flint45 won by MiMo-V2.6-Flash105 tied