MiniMax M2.1
minimax/minimax-m2.1InputOutput
Compare its 3 providersIncident RSSCompare with MiniMax M2, MiniMax M2-her, MiniMax M2.5
CompareMiniMax M2.1
- No data24h 99.75%
- 7d
- 100%
- 30d
- 99.96%
- p50
- 2.58s
- p99
- 3.62s
- Throughput
- 80 tps
- Context
- 205K
- $/Mtok
- $0.300 / $1.20
minimax/fp8fp8 - No data24h 99.33%
- 7d
- 99.87%
- 30d
- 99.94%
- p50
- 1.45s
- p99
- 4.94s
- Throughput
- 34 tps
- Context
- 205K
- $/Mtok
- $0.300 / $2.40
minimax/highspeedfp8 - No data24h 99.69%
- 7d
- 99.50%
- 30d
- 99.64%
- p50
- 1.46s
- p99
- 4.33s
- Throughput
- 53 tps
- Context
- 205K
- $/Mtok
- $0.300 / $1.20
novita/fp8fp8
Measured 4m ago. Latency and throughput are OpenRouter's rolling 30-minute windows.
History
Availability
Axis starts at 90% so small differences stay visible; it expands to 0 when an endpoint falls below.
Time to first token
Logarithmic axis — the fleet spans two orders of magnitude. P50 is OpenRouter's rolling 30-minute window, averaged over the hour.
Throughput
Median tokens per second.
Daily availability
One row per endpoint · one dot per day · last 90 days.
worst hour ≥ 95%90–95%< 90%no data
Colour by each endpoint's worst hour of each UTC day · 3 endpoints · 47 days with data, none below the red threshold.