Model retirement dates / Groq

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

Groq retired meta-llama/llama-guard-4-12b on 5 March 2026. Calls to it now fail. Groq recommends openai/gpt-oss-safeguard-20b. This is Groq's date for its API; the model's maker and other hosts set their own.

ProviderGroq (hosts other makers' models)
Modelmeta-llama/llama-guard-4-12b by Meta
StatusRetired (as of 14 Nov 2026)
Shutdown5 March 2026
Replacementopenai/gpt-oss-safeguard-20b
Moving to itAPI change · gpt-oss-safeguard checks text against a policy you write in the system prompt and answers in the format you ask for. Llama Guard's fixed categories and safe/unsafe answer don't carry over. Groq's guide
Model typeText
SourceGroq: deprecations

How Driftline finds it

meta-llama/llama-guard-4-12b could also mean something else (other services use the same name for their own copy of the model), so Driftline counts it only in files that show they call Groq: groq imports, GROQ_API_KEY or api.groq.com, or a groq/ prefix.

Check your code for it

Run this in your repository. No install and no API key; it lists every OpenAI, Anthropic, Google, Mistral, xAI, Cohere, DeepSeek, Groq, Bedrock, Vertex AI and Azure model ID it finds, with its retirement date and replacement:

npx -y @aidriftline/driftline .

Or look for this ID only: grep -rn "meta-llama/llama-guard-4-12b" . (misses aliases, Bedrock and Vertex names, and IDs split across lines).

To be warned automatically before the next retirement, add the free Driftline GitHub Action. It annotates the exact line in pull requests and can fail the build on retired models.

Where a new name is the whole change, Driftline can make it for you: npx -y @aidriftline/driftline fix --dry-run shows the edits, and the Action's fix-pr: true opens one pull request with them, plus a checklist for the lines that need more. See an example pull request.

Read from Groq's official page on 14 November 2026, checked every 6 hours. Something wrong? hello@aidriftline.com