Skip to content

Highest Output-Speed Nex-N2-Pro Inference Providers

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

SiliconFlow currently ranks first at 67.0 tok/s via siliconflow.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Nex-N2-Pro Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
SiliconFlowsiliconflow
Output speed67.0 tok/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
#2Provider / route
Nex AGInex-agi/fp8
Output speed59.0 tok/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

Endpoint data fetched .

Nex-N2-Pro endpoint guide

How to interpret the Highest Output-Speed Nex-N2-Pro Inference Providers

2 of 2 Nex-N2-Pro endpoints currently have the published data required for this ranking. SiliconFlow leads at 67.0 tok/s via siliconflow. 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 SiliconFlow with the next option

Nex AGI currently ranks second at 59.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

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.