Favicon for meta-llama

Meta: Llama Guard 4 12B

meta-llama/llama-guard-4-12b

Model weights

Llama Guard 4 is a Llama 4 Scout-derived multimodal pretrained model, fine-tuned for content safety classification. Similar to previous versions, it can be used to classify content in both LLM inputs (prompt classification) and in LLM responses (response classification). It acts as an LLM—generating text in its output that indicates whether a given prompt or response is safe or unsafe, and if unsafe, it also lists the content categories violated.

Llama Guard 4 was aligned to safeguard against the standardized MLCommons hazards taxonomy and designed to support multimodal Llama 4 capabilities. Specifically, it combines features from previous Llama Guard models, providing content moderation for English and multiple supported languages, along with enhanced capabilities to handle mixed text-and-image prompts, including multiple images. Additionally, Llama Guard 4 is integrated into the Llama Moderations API, extending robust safety classification to text and images.

Modalities
In / out price
$0.18 / $0.18per 1M
Context
164K
Released
Apr 30, 2025
Knowledge cutoff
Aug 2024

Providers

Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick: Balanced (price + speed), Nitro (fastest), or Floor (cheapest).

  • Not used in Standard routing:Why these endpoints are not used

Pricing

The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.

Weighted average

Input
$0.2036/M tokens
Output
$0.08876/M tokens
Price history
No effective price data for this selection
  • Not used in Standard routing:Why these endpoints are not used

Performance

Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).

Throughput
54tok/s

P50, best across providers

Latency
0.27s

P50, best provider

Uptime

Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.

Uptime (3d)The model was reachable. Request routed to a provider.
100.00%
Availability (3d)The model returned inference from any provider. Errors and empty responses count against it.
99.54%

Availability over the last 3 days

Last 72 hours
Availability 99.54%
3 Days Ago2 Days AgoYesterdayNow

Availability over the last 24 hours

OpenRouter Availability
99.66%

When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and provider routing options.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

1.
157Mtokens
2.
140Mtokens
4.
82.8Mtokens
Rest of OpenRouter
104M
Top 5 Apps
16.7M

Activity

Token volume and request traffic to this model over time.

API

Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.

Not currently available through EU in-region routing. In-region routing docs

Frequently asked questions