Skip to content

Fastest Mistral Small 4 Inference Providers

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

Mistral currently ranks first at 5.39 s via mistral.

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

Fastest response endpoint ranking

Fastest Mistral Small 4 Inference Providers
RankProvider / routeEstimated response timeSpeed measurementsEndpoint details
#1Provider / route
Mistralmistral
Estimated response time5.39 sSpeed measurements
500-token response
5.39 s
Response starts
0.39 s
Output speed
100.0 tok/s
Endpoint details
Input price
$0.15 / 1M tokens
Output price
$0.6 / 1M tokens
Uptime (30 min)
100.00%
Context
262.1K
#2Provider / route
Venicevenice/fp8
Estimated response time31.80 sSpeed measurements
500-token response
31.80 s
Response starts
0.55 s
Output speed
16.0 tok/s
Endpoint details
Input price
$0.1875 / 1M tokens
Output price
$0.75 / 1M tokens
Uptime (30 min)
99.77%
Context
256K

Endpoint data fetched .

Mistral Small 4 endpoint guide

How to interpret the Fastest Mistral Small 4 Inference Providers

2 of 2 Mistral Small 4 endpoints currently have the published data required for this ranking. Mistral leads at 5.39 s via mistral. 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 Mistral with the next option

Venice currently ranks second at 31.80 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

Mistral Small 4 has 2 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.