MiniMax M3.1 Flash Preview
MiniMax M3.1 Flash Preview · max, showing maintainability. Results for all tested efforts are available below.
Maintainability53
MiniMax M3.1 Flash Preview · max
- Backend engineering
- 71
- Frontend interaction
- 53
- Knowledge & reasoning
- 75
- Visual aesthetics
- 70
- Maintainability
- 53
- Evaluation time
- —
- Cost
- —
Maintainability · Evaluation time & API cost
Results by reasoning effort
Swipe to see all results →
| Model / effort | Overall | Backend engineering | Frontend interaction | Knowledge & reasoning | Visual aesthetics | Maintainability | Total eval. time | Total ref. cost | Compare |
|---|---|---|---|---|---|---|---|---|---|
| — | 30 | — | — | — | — | 3m 21s | — | ||
| — | 34 | — | — | — | — | 4m 28s | — | ||
| — | 63 | — | 75 | — | — | 28m 29s | — | ||
| — | 47 | 15 | — | — | — | 17m 55s | — | ||
| 66.00 | 71 | 53 | 75 | 70 | 53 | 54m 7s | — |
Score breakdown
- Overall score
- 66.00
- Evaluation time
- 54m 7s
- Cost
- N/A
Code readability, organization and the cost of change.
Semantic clarity16 / 20
Naming, explicit responsibilities and readability.
Control-flow organization20 / 20
Execution paths, responsibility boundaries and logical structure.
Locality of changes14 / 20
The scope of rule changes and duplicated maintenance.
State and lifecycle15 / 20
State ownership, cleanup and lifecycle management.
Implementation economy16 / 20
Implementation complexity, useful abstractions and redundancy.
Subscores retain their original scale; the axis score uses a consistent conversion.
What changes with higher reasoning effort
Compare maintainability scores, cost, and time across neighboring tested efforts.
xhigh max
- Maintainability
- — — → 53.00
- Cost
- — — → —
- Evaluation time
- — — → —
Data snapshot published · 11/13/2026Scoring & cost notes