Skip to content

Highest Output-Speed Mistral Small 4 Inference Providers

Ranks providers by their recent typical output speed in tokens per second. Providers without enough recent data remain visible after ranked rows.

Mistral currently ranks first at 100.0 tok/s via mistral.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Mistral Small 4 Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Mistralmistral
Output speed100.0 tok/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
Output speed16.0 tok/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 Highest Output-Speed Mistral Small 4 Inference Providers

2 of 2 Mistral Small 4 endpoints currently have the published data required for this ranking. Mistral leads at 100.0 tok/s via mistral. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How generation throughput is ranked

The output-speed ranking compares recent median generated tokens per second. It favors routes that complete long generations quickly, while first-token latency remains a separate measure of how responsive the endpoint feels at the beginning.

Compare Mistral with the next option

Venice currently ranks second at 16.0 tok/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.