Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
Venice currently ranks first at 5.47 s via venice.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Venice venice | Estimated response time5.47 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route DeepInfra deepinfra/fp4 | Estimated response time8.27 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route StreamLake streamlake/fp8 | Estimated response time11.39 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Phala phala | Estimated response time11.64 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Moonshot AI moonshotai/int4 | Estimated response time13.15 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route SiliconFlow siliconflow/int4 | Estimated response time14.04 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route ModelRun modelrun/fp4 | Estimated response time17.03 s | Speed measurements
| Endpoint details
|
| #8 | Provider / route AtlasCloud atlas-cloud/int4 | Estimated response time18.66 s | Speed measurements
| Endpoint details
|
| #9 | Provider / route NovitaAI novita | Estimated response time19.26 s | Speed measurements
| Endpoint details
|
| #10 | Provider / route Chutes chutes/int4 | Estimated response time30.67 s | Speed measurements
| Endpoint details
|
| #11 | Provider / route DigitalOcean digitalocean | Estimated response time42.51 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Kimi K2.5 endpoint guide
11 of 11 Kimi K2.5 endpoints currently have the published data required for this ranking. Venice leads at 5.47 s via venice. 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.
DeepInfra currently ranks second at 8.27 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.
Kimi K2.5 has 11 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.
