Skip to content

Fastest GPT-5.1-Codex-Mini Inference Providers

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

Azure currently ranks first at 6.52 s via azure.

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

Fastest response endpoint ranking

Fastest GPT-5.1-Codex-Mini Inference Providers
RankProvider / routeEstimated response timeSpeed measurementsEndpoint details
#1Provider / route
Azureazure
Estimated response time6.52 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
Estimated response time6.91 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 Fastest 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 6.52 s via azure. 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 Azure with the next option

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