Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
StreamLake currently ranks first at 22.65 s via streamlake.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route StreamLake streamlake | Estimated response time22.65 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route AtlasCloud atlas-cloud/fp8 | Estimated response time501.17 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
KAT-Coder-Pro V2 endpoint guide
2 of 2 KAT-Coder-Pro V2 endpoints currently have the published data required for this ranking. StreamLake leads at 22.65 s via streamlake. 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.
AtlasCloud currently ranks second at 501.17 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.
KAT-Coder-Pro V2 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.
