Skip to content

Highest Output-Speed Llama Guard 4 12B Inference Providers

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

Together currently ranks first at 16.0 tok/s via together.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Llama Guard 4 12B Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Togethertogether
Output speed16.0 tok/sSpeed measurements
500-token response
31.38 s
Response starts
0.13 s
Output speed
16.0 tok/s
Endpoint details
Input price
$0.2 / 1M tokens
Output price
$0.2 / 1M tokens
Uptime (30 min)
100.00%
Context
1M
#2Provider / route
DeepInfradeepinfra/bf16
Output speed9.0 tok/sSpeed measurements
500-token response
55.85 s
Response starts
0.29 s
Output speed
9.0 tok/s
Endpoint details
Input price
$0.18 / 1M tokens
Output price
$0.18 / 1M tokens
Uptime (30 min)
99.98%
Context
163.8K

Endpoint data fetched .

Llama Guard 4 12B endpoint guide

How to interpret the Highest Output-Speed Llama Guard 4 12B Inference Providers

2 of 2 Llama Guard 4 12B endpoints currently have the published data required for this ranking. Together leads at 16.0 tok/s via together. 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 Together with the next option

DeepInfra currently ranks second at 9.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

Llama Guard 4 12B 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.