Skip to content

Highest Output-Speed Claude Sonnet 4.5 Inference Providers

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

Anthropic currently ranks first at 40.5 tok/s via anthropic/2.

Provider options:
8
Ranked:
5
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Claude Sonnet 4.5 Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Anthropicanthropic/2
Output speed40.5 tok/sSpeed measurements
500-token response
15.55 s
Response starts
3.21 s
Output speed
40.5 tok/s
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
1M
#2Provider / route
Anthropicanthropic
Output speed36.0 tok/sSpeed measurements
500-token response
15.30 s
Response starts
1.42 s
Output speed
36.0 tok/s
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
99.43%
Context
1M
#3Provider / route
Google Vertexgoogle-vertex/global
Output speed35.0 tok/sSpeed measurements
500-token response
15.58 s
Response starts
1.30 s
Output speed
35.0 tok/s
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
100.00%
Context
1M
#4Provider / route
Amazon Bedrockamazon-bedrock
Output speed33.0 tok/sSpeed measurements
500-token response
16.61 s
Response starts
1.46 s
Output speed
33.0 tok/s
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
99.97%
Context
1M
#5Provider / route
Google Vertexgoogle-vertex/us-east5
Output speed3.0 tok/sSpeed measurements
500-token response
167.54 s
Response starts
0.87 s
Output speed
3.0 tok/s
Endpoint details
Input price
$3.3 / 1M tokens
Output price
$16.5 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
1M
Provider / route
Azureazure/us-east-2
Output speedInsufficient recent dataSpeed measurements
500-token response
Insufficient recent data
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
200K
Provider / route
Anthropicanthropic/claude-on-aws
Output speedInsufficient recent dataSpeed measurements
500-token response
Insufficient recent data
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Input price
$3 / 1M tokens
Output price
$15 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
1M
Provider / route
Amazon Bedrockamazon-bedrock/eu-west-1
Output speedInsufficient recent dataSpeed measurements
500-token response
Insufficient recent data
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Input price
$3.3 / 1M tokens
Output price
$16.5 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
1M

Endpoint data fetched .

Claude Sonnet 4.5 endpoint guide

How to interpret the Highest Output-Speed Claude Sonnet 4.5 Inference Providers

5 of 8 Claude Sonnet 4.5 endpoints currently have the published data required for this ranking. Anthropic leads at 40.5 tok/s via anthropic/2. 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 Anthropic with the next option

Anthropic currently ranks second at 36.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

Claude Sonnet 4.5 has 8 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.