Skip to content

Fastest Nova Micro 1.0 Inference Providers

Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.

Amazon Bedrock currently ranks first at 5.21 s via amazon-bedrock.

Provider options:
2
Ranked:
2
Metric:
Estimated response time

Fastest response endpoint ranking

Fastest Nova Micro 1.0 Inference Providers
RankProvider / routeEstimated response timeSpeed measurementsEndpoint details
#1Provider / route
Amazon Bedrockamazon-bedrock
Estimated response time5.21 sSpeed measurements
500-token response
5.21 s
Response starts
0.31 s
Output speed
102.0 tok/s
Endpoint details
Input price
$0.035 / 1M tokens
Output price
$0.14 / 1M tokens
Uptime (30 min)
100.00%
Context
128K
#2Provider / route
Amazon Bedrockamazon-bedrock/eu-west-1
Estimated response time10.04 sSpeed measurements
500-token response
10.04 s
Response starts
0.43 s
Output speed
52.0 tok/s
Endpoint details
Input price
$0.035 / 1M tokens
Output price
$0.14 / 1M tokens
Uptime (30 min)
68.23%
Context
128K

Endpoint data fetched .

Nova Micro 1.0 endpoint guide

How to interpret the Fastest Nova Micro 1.0 Inference Providers

2 of 2 Nova Micro 1.0 endpoints currently have the published data required for this ranking. Amazon Bedrock leads at 5.21 s via amazon-bedrock. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How complete response time is ranked

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.

Compare Amazon Bedrock with the next option

Amazon Bedrock currently ranks second at 10.04 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

Nova Micro 1.0 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.