Skip to content

Fastest Nex-N2-Pro Inference Providers

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

Nex AGI currently ranks first at 9.45 s via nex-agi/fp8.

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

Fastest response endpoint ranking

Fastest Nex-N2-Pro Inference Providers
RankProvider / routeEstimated response timeSpeed measurementsEndpoint details
#1Provider / route
Nex AGInex-agi/fp8
Estimated response time9.45 sSpeed measurements
500-token response
9.45 s
Response starts
0.98 s
Output speed
59.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$1 / 1M tokens
Uptime (30 min)
99.65%
Context
262.1K
#2Provider / route
SiliconFlowsiliconflow
Estimated response time9.89 sSpeed measurements
500-token response
9.89 s
Response starts
2.43 s
Output speed
67.0 tok/s
Endpoint details
Input price
$0.5 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
262.1K

Endpoint data fetched .

Nex-N2-Pro endpoint guide

How to interpret the Fastest Nex-N2-Pro Inference Providers

2 of 2 Nex-N2-Pro endpoints currently have the published data required for this ranking. Nex AGI leads at 9.45 s via nex-agi/fp8. 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 Nex AGI with the next option

SiliconFlow currently ranks second at 9.89 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

Nex-N2-Pro 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.