Skip to content

Highest Output-Speed GPT-5.1-Codex-Mini Inference Providers

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

Azure currently ranks first at 120.0 tok/s via azure.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed GPT-5.1-Codex-Mini Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Azureazure
Output speed120.0 tok/sSpeed measurements
500-token response
6.52 s
Response starts
2.36 s
Output speed
120.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
400K
#2Provider / route
OpenAIopenai
Output speed94.0 tok/sSpeed measurements
500-token response
6.91 s
Response starts
1.59 s
Output speed
94.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$2 / 1M tokens
Uptime (30 min)
98.82%
Context
400K

Endpoint data fetched .

GPT-5.1-Codex-Mini endpoint guide

How to interpret the Highest Output-Speed GPT-5.1-Codex-Mini Inference Providers

2 of 2 GPT-5.1-Codex-Mini endpoints currently have the published data required for this ranking. Azure leads at 120.0 tok/s via azure. 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 Azure with the next option

OpenAI currently ranks second at 94.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

GPT-5.1-Codex-Mini 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.