Skip to content

Fastest MiniMax M2.5 Inference Providers

Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.

MARA currently ranks first at 3.14 s via mara.

Provider options:
16
Ranked:
16
Metric:
Estimated response time

Fastest response endpoint ranking

Fastest MiniMax M2.5 Inference Providers
RankProvider / routeEstimated response timeSpeed measurementsEndpoint details
#1Provider / route
MARAmara
Estimated response time3.14 sSpeed measurements
500-token response
3.14 s
Response starts
1.02 s
Output speed
236.0 tok/s
Endpoint details
Input price
$0.24 / 1M tokens
Output price
$0.96 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#2Provider / route
Friendlifriendli
Estimated response time4.08 sSpeed measurements
500-token response
4.08 s
Response starts
0.47 s
Output speed
138.5 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#3Provider / route
Parasailparasail/fp8
Estimated response time4.51 sSpeed measurements
500-token response
4.51 s
Response starts
0.54 s
Output speed
126.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#4Provider / route
StreamLakestreamlake
Estimated response time4.60 sSpeed measurements
500-token response
4.60 s
Response starts
0.62 s
Output speed
125.5 tok/s
Endpoint details
Input price
$0.27 / 1M tokens
Output price
$1.08 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
200K
#5Provider / route
Estimated response time6.45 sSpeed measurements
500-token response
6.45 s
Response starts
0.50 s
Output speed
84.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#6Provider / route
DigitalOceandigitalocean
Estimated response time8.28 sSpeed measurements
500-token response
8.28 s
Response starts
0.59 s
Output speed
65.0 tok/s
Endpoint details
Input price
$0.225 / 1M tokens
Output price
$0.9 / 1M tokens
Uptime (30 min)
100.00%
Context
65.5K
#7Provider / route
Inceptroninceptron/fp8
Estimated response time9.09 sSpeed measurements
500-token response
9.09 s
Response starts
0.47 s
Output speed
58.0 tok/s
Endpoint details
Input price
$0.15 / 1M tokens
Output price
$0.9 / 1M tokens
Uptime (30 min)
100.00%
Context
196.6K
#8Provider / route
DeepInfradeepinfra/fp8
Estimated response time9.63 sSpeed measurements
500-token response
9.63 s
Response starts
0.54 s
Output speed
55.0 tok/s
Endpoint details
Input price
$0.15 / 1M tokens
Output price
$1.15 / 1M tokens
Uptime (30 min)
100.00%
Context
196.6K
#9Provider / route
MiniMaxminimax/fp8
Estimated response time10.51 sSpeed measurements
500-token response
10.51 s
Response starts
1.74 s
Output speed
57.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
204.8K
#10Provider / route
Venicevenice
Estimated response time10.55 sSpeed measurements
500-token response
10.55 s
Response starts
0.84 s
Output speed
51.5 tok/s
Endpoint details
Input price
$0.27 / 1M tokens
Output price
$0.95 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
198K
#11Provider / route
SiliconFlowsiliconflow/fp8
Estimated response time11.24 sSpeed measurements
500-token response
11.24 s
Response starts
1.24 s
Output speed
50.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#12Provider / route
MiniMaxminimax/highspeed
Estimated response time12.53 sSpeed measurements
500-token response
12.53 s
Response starts
2.11 s
Output speed
48.0 tok/s
Endpoint details
Input price
$0.6 / 1M tokens
Output price
$2.4 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
204.8K
#13Provider / route
Chuteschutes/fp8
Estimated response time15.22 sSpeed measurements
500-token response
15.22 s
Response starts
1.71 s
Output speed
37.0 tok/s
Endpoint details
Input price
$0.15 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
89.52%
Context
196.6K
#14Provider / route
Phalaphala
Estimated response time15.63 sSpeed measurements
500-token response
15.63 s
Response starts
1.74 s
Output speed
36.0 tok/s
Endpoint details
Input price
$0.2 / 1M tokens
Output price
$1.38 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K
#15Provider / route
NovitaAInovita/fp8
Estimated response time57.18 sSpeed measurements
500-token response
57.18 s
Response starts
1.62 s
Output speed
9.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
204.8K
#16Provider / route
AtlasCloudatlas-cloud/fp8
Estimated response time64.71 sSpeed measurements
500-token response
64.71 s
Response starts
2.21 s
Output speed
8.0 tok/s
Endpoint details
Input price
$0.295 / 1M tokens
Output price
$1.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
196.6K

Endpoint data fetched .

MiniMax M2.5 endpoint guide

How to interpret the Fastest MiniMax M2.5 Inference Providers

16 of 16 MiniMax M2.5 endpoints currently have the published data required for this ranking. MARA leads at 3.14 s via mara. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How complete response time is ranked

The fastest ranking estimates a 500-token answer by adding the recent median first-token wait to 500 divided by median output throughput. It represents an example complete response, not a guarantee for every prompt or request size.

Compare MARA with the next option

Friendli currently ranks second at 4.08 s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.

Use the route, not only the provider name

MiniMax M2.5 has 16 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.