Start typing to search.
Ranks providers by their recent typical output speed in tokens per second. Providers without enough recent data remain visible after ranked rows.
OpenAI currently ranks first at 63.0 tok/s via openai.
| Rank | Provider / route | Output speed | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route OpenAI openai | Output speed63.0 tok/s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Azure azure | Output speed55.0 tok/s | Speed measurements
| Endpoint details
|
| — | Provider / route OpenAI openai/priority | Output speedInsufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
GPT-5.3-Codex endpoint guide
2 of 3 GPT-5.3-Codex endpoints currently have the published data required for this ranking. OpenAI leads at 63.0 tok/s via openai. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
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.
Azure currently ranks second at 55.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.
GPT-5.3-Codex has 3 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.
