MiniMax M3.1 Flash Preview released
MiniMax · Model release
Source confirmed
Data as of September 27, 2026 · How the score is built
CurrentProprietaryReasoning
MiniMax M3.1 Flash Preview
Decision readingMiniMax M3.1 Flash Preview is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Released Sep 27, 2026 — see all recent releases
MiniMax M3.1 Flash Preview will be repriced, updated or retired. Get each notice with its source and date. Follow model changes
Share or export
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
preview · Preview
Radar
Full release historyMiniMax M3.1 Flash Preview release history
Radar confirmed these at the source. Use MiniMax M3.1 Flash Preview in your work? Explore Radar to follow supported changes and choose your alerts.
Radar
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- Not published
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not disclosed by the provider
- Availability
- Available in MiniMax Code as M3.1-Flash-Preview. API and open-weight availability have not been announced in the source provided.
- Cloud regions
- Not tracked yet
- Lifecycle
- Current
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- Weights are not published
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track MiniMax M3.1 Flash Preview, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
MiniMax M3.1 Flash Preview is a proprietary model. It uses an explicit reasoning mode, which can improve complex problem solving while adding latency and token use.
Available in MiniMax Code as M3.1-Flash-Preview. API and open-weight availability have not been announced in the source provided.
MiniMax announced M3.1-Flash-Preview for MiniMax Code on September 27, 2026. The launch image shows selectable effort levels from low through max. No benchmark results, context limit, API model ID, token price, or open-weight release were provided in the announcement. This row remains unranked until model-specific evidence is available.
The profile has no source-displayable benchmark row yet.
Last updated September 27, 2026. Runtime fields remain blank until a sourced snapshot exists.
Questions
How does MiniMax M3.1 Flash Preview perform overall in AI benchmarks?
MiniMax M3.1 Flash Preview does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Does MiniMax M3.1 Flash Preview have full benchmark coverage on BenchLM?
No. MiniMax M3.1 Flash Preview currently has 0 source-displayable rows across 486 tracked benchmark slots. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of MiniMax M3.1 Flash Preview?
MiniMax M3.1 Flash Preview's context window is not documented in a source tied to this exact model yet. The profile leaves the value unavailable instead of borrowing a limit from an earlier family member or an unverified route. Maximum output length remains a separate field.