Head to head · Guard moderation · October 2026 research run

Granite Guardian vs Llama Guard 4

Granite Guardian scores 60.1 (C) on agent readiness against Llama Guard 4's 49.1 (D), and leads in every scored category. Both do guard moderation.

Which one, for what

Granite Guardian C

Good for A team with a GPU that wants one English-language judge for harm, jailbreaks, RAG groundedness, function-call checks and house rules, under a permissive licence with no gate.

Ahead on

  • Reliability, 56 against 38
  • Schema & documentation, 60 against 52
  • Security & auth, 58 against 53
  • Payments & pricing, 60 against 45
  • Maintenance & community, 47 against 28
  • Transparency & trust, 70 against 55

Watch for

Trained and tested on English only, per the model card

Llama Guard 4 D

Good for A team outside the EU with a GPU that wants content moderation of text and images on its own hardware, against a fixed 14-category policy it can edit in the prompt.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Weights last changed on 29 April 2025, with no changelog, version tags or stated deprecation policy

Score by category

CategoryWeight this runGranite GuardianLlama Guard 4Edge
Reliability16%205638Granite Guardian +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26052Granite Guardian +8
Agent ergonomics13%16.26967Granite Guardian +2
Security & auth14%17.55853Granite Guardian +5
Payments & pricing10%12.56045Granite Guardian +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84728Granite Guardian +19
Transparency & trust7%8.87055Granite Guardian +15
Negative events≤1500
Total60.1 · C49.1 · D

Facts side by side

FactGranite GuardianLlama Guard 4
KindModel APIModel API
VendorIBMMeta
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache 2.0 for the weights and the repositoryLlama 4 Community Licence (source-available weights, not an OSI licence), with the Llama 4 acceptable use policy
Read-only variant documentednono
llms.txtnono
Last release2026-04-292025-04-29
Terms last updatedno document linked2025-04-05
Privacy policy last updatedno document linkedno document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity182 stars4.4k stars

Verdicts

Granite Guardian

One ungated Apache 2.0 model judges harm, jailbreaks, RAG groundedness, function-call errors and custom criteria, with signed weights and published evaluation code. It is trained and tested on English only, each call checks one criterion, the 4.1 prompt format differs from 3.x, and IBM's watsonx.ai lists only the deprecated 3.0 model.

Llama Guard 4

A single self-hosted model classifies text and multi-image prompts against 14 MLCommons-aligned hazard categories and answers in a few tokens. The weights have not changed since 29 April 2025, download access needs Meta's manual approval, and the licence withholds the grant from individuals and companies based in the European Union.

Before you call either

Granite Guardian

  1. Append the <guardian> block as the final user message, with the mode line, ### Criteria: and ### Scoring Schema:. Copy the strings from the model card, because no package builds them
  2. Use the no-think instruction for gating and parse <score>. Think mode writes a reasoning trace first, and the card's examples allow up to 2,048 output tokens
  3. Treat yes as the criterion being met, which for built-in criteria means the risk is present. Treat a missing <score> tag as a failed check
  4. Pass retrieved text through documents= and tool schemas through available_tools= in apply_chat_template, not inside the message text
  5. Under Ollama, set num_ctx in the request options. IBM's docs say the default context is short and long requests are truncated

Llama Guard 4

  1. Request access on the Hugging Face page before anything else. Approval is manual, and the form cannot be edited after submission
  2. Send only the user turn to check an input, and the user turn plus the model's answer to check an output. The template picks the role from the message count
  3. Parse the first line for safe or unsafe and the second for category codes. Set max_new_tokens to about 10 and turn sampling off
  4. Do not send an image with no text. Meta says the model is not an image-only classifier, and S14 is skipped when an image is present
  5. Pair it with a prompt-attack detector. The card says the model can itself be moved by adversarial or injected text

Questions

Which is better for AI agents, Granite Guardian or Llama Guard 4?

Granite Guardian scores 60.1 (C) on agent readiness against Llama Guard 4's 49.1 (D), and leads in every scored category.

Do Granite Guardian and Llama Guard 4 need an API key?

Neither needs a key.

Can an agent call Granite Guardian and Llama Guard 4 without installing anything?

No hosted endpoint is listed for Granite Guardian. No hosted endpoint is listed for Llama Guard 4.

Other comparisons with Granite Guardian or Llama Guard 4

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.