Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
DeepInfra currently ranks first at 14.85 s via deepinfra/fp4.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route DeepInfra deepinfra/fp4 | Estimated response time14.85 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route NovitaAI novita/bf16 | Estimated response time17.10 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Z.ai z-ai/fp4 | Estimated response time18.62 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Venice venice/fp4 | Estimated response time27.42 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route AtlasCloud atlas-cloud/fp8 | Estimated response time43.14 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
GLM 4.6 endpoint guide
5 of 5 GLM 4.6 endpoints currently have the published data required for this ranking. DeepInfra leads at 14.85 s via deepinfra/fp4. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
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.
NovitaAI currently ranks second at 17.10 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.
GLM 4.6 has 5 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.
