Start typing to search.
Ranks providers by how quickly the first generated token appears. Providers without enough recent data remain visible after ranked rows.
ModelRun currently ranks first at 0.36 s via modelrun/fp4.
| Rank | Provider / route | Time to first token | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route ModelRun modelrun/fp4 | Time to first token0.36 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route DeepInfra deepinfra/fp4 | Time to first token0.81 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route DigitalOcean digitalocean | Time to first token0.84 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Moonshot AI moonshotai/int4 | Time to first token0.96 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Venice venice | Time to first token1.07 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route Chutes chutes/int4 | Time to first token1.26 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route StreamLake streamlake/fp8 | Time to first token1.39 s | Speed measurements
| Endpoint details
|
| #8 | Provider / route AtlasCloud atlas-cloud/int4 | Time to first token1.42 s | Speed measurements
| Endpoint details
|
| #9 | Provider / route Phala phala | Time to first token1.44 s | Speed measurements
| Endpoint details
|
| #10 | Provider / route SiliconFlow siliconflow/int4 | Time to first token1.54 s | Speed measurements
| Endpoint details
|
| #11 | Provider / route NovitaAI novita | Time to first token4.11 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. ModelRun leads at 0.36 s via modelrun/fp4. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The first-token ranking orders endpoints by the recent median time before output begins. This is useful for interactive applications, but it should be read alongside throughput because the first provider to start is not always the first to finish a long answer.
DeepInfra currently ranks second at 0.81 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.
