Skip to content

Highest Output-Speed Kimi K2 0905 Inference Providers

Ranks providers by their recent typical output speed in tokens per second. Providers without enough recent data remain visible after ranked rows.

Groq currently ranks first at 70.0 tok/s via groq.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Kimi K2 0905 Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Groqgroq
Output speed70.0 tok/sSpeed measurements
500-token response
7.50 s
Response starts
0.35 s
Output speed
70.0 tok/s
Endpoint details
Input price
$1 / 1M tokens
Output price
$3 / 1M tokens
Uptime (30 min)
99.97%
Context
262.1K
#2Provider / route
NovitaAInovita/fp8
Output speed14.0 tok/sSpeed measurements
500-token response
36.79 s
Response starts
1.08 s
Output speed
14.0 tok/s
Endpoint details
Input price
$0.6 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
98.94%
Context
262.1K

Endpoint data fetched .

Kimi K2 0905 endpoint guide

How to interpret the Highest Output-Speed Kimi K2 0905 Inference Providers

2 of 2 Kimi K2 0905 endpoints currently have the published data required for this ranking. Groq leads at 70.0 tok/s via groq. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How generation throughput is ranked

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.

Compare Groq with the next option

NovitaAI currently ranks second at 14.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.

Use the route, not only the provider name

Kimi K2 0905 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.