Head to head · Content moderation · October 2026 research run
Mistral Moderation API vs NVIDIA NeMo Guardrails
NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Mistral Moderation API's 63.1 (B), and leads in 2 of 7 scored categories. Mistral Moderation API leads on schema & documentation, agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do content moderation.
Best guardrails and safety filters for AI agents · All 157 guardrails comparisons
Which one, for what
Best for A free classifier for an agent that also needs PII, jailbreak and advice categories, or for a Mistral-hosted agent that can set the guardrail inline.
Ahead on
- Schema & documentation, 88 against 79
- Agent ergonomics, 75 against 67
- Security & auth, 70 against 62
- Maintenance & community, 83 against 70
- Transparency & trust, 80 against 72
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No moderation component on the status page, and its history couldn't be read for the last 90 days
Best for Teams that want to compose several checks (their own, NVIDIA's and third-party APIs) behind one OpenAI-compatible endpoint.
Ahead on
- Reliability, 75 against 43
- Payments & pricing, 90 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Open source
- No incidents deducted, where Mistral Moderation API loses 6 points for them
Watch for
Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability NVIDIA NeMo Guardrails +32
Mistral Moderation API 43
status.mistral.ai runs on Rootly with 90-day uptime bars per component, but none of its components is for moderation, per the 1 October check (10 of 20, our call for a status page that doesn't cover the endpoint). The page has answered with a Cloudflare bot check since 8 October, robots.txt included on 4 November, so the host is treated as blocked and the 90 days from 6 August were not read (5, unread and not a finding against the vendor), as the other Mistral listings read it. The usage and limits page says API rate limits are shown in the Admin Panel, with no published numbers (3 of 15, as the other Mistral listings read the same page). The error glossary tells callers to back off exponentially on 429, 500, 502, 503 and 504 and to check the Retry-After header, and the official SDKs retry with backoff. The zero data retention page lists /v1/moderations and /v1/chat/moderations as stateless calls, so no write is involved (15, as the OCR and transcription listings). No SLA found (0). mistral-moderation-2603 is GA (10). 10+5+3+15+0+10 = 43.
NVIDIA NeMo Guardrails 75
Local framework reading. Installs from PyPI as nemoguardrails, pyproject on develop states Python 3.10 to 3.13 (20). The README carries passing badges for tests on Linux, Windows and macOS and for lint on the develop branch, per the 1 October check, not re-read on 1 November (25). About 140 open issues and 80 to 100 open pull requests, with bug reports from August 2026 still labelled needs triage beside others already triaged, per the 1 October check, not re-read on 1 November (15 of 25). The changelog follows Keep a Changelog and marks breaking items, six of them in 0.24.0 (15). Version 0.24.1, not 1.0, and develop now reads 0.25.0-rc1, unreleased (0).
Payments & pricing NVIDIA NeMo Guardrails +30
Mistral Moderation API 60
No x402, MPP or L402 (0). Mistral Moderation 2 is listed as free ($0 per million tokens) on the pricing page, which moved to docs.mistral.ai/inference/pricing, re-read on 4 November (20). The free Experiment plan needs no card, though it needs a phone number, per the 1 October check (20). A person signs up in a browser and verifies a phone (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
NVIDIA NeMo Guardrails 90
Apache-2.0 package you run yourself with nothing to buy from the project, so 20 for pricing, 20 for a free start and 20 for keyless use. No payment protocol (0). The NemoGuard models it can call are priced separately by NVIDIA. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community Mistral Moderation API +13
Mistral Moderation API 83
Mistral's SDKs cover every Mistral API, so their releases count here only where they change moderation code, as the Vonage and Groq listings read umbrella SDKs. Python 3.3.0 and TypeScript 3.1.0 (20 October 2026, per each repository's RELEASES.md) change the type field in classifiers.moderate_chat(), 15 days before this check (30). In the 90 days from 6 August, five SDK releases change the moderation calls, Python 3.0.0 (28 September, mistral_mcp across the classifier operations), Python 3.1.0 (6 October, resource variants in moderate_chat()), TypeScript 3.0.0 (7 October, moderateChat() inputs) and Python 3.3.0 and TypeScript 3.1.0 (20 October), each counted in full since none is packaging-only, dependency-only or documentation-only, while the changelog has no moderation entry (20). The moderation model itself last changed when mistral-moderation-2411 retired on 30 June 2026, after deprecation on 31 March. Dated changelog and docs and support through the console (10 of 15). Current official SDKs, mistralai 3.7.0 and @mistralai/mistralai 3.5.0 (1 November) (15). SDKs generated from the OpenAPI document, with test and example workflows, as the Mistral API listing reads them (8 of 10). 30+20+10+15+8 = 83.
NVIDIA NeMo Guardrails 70
0.24.1 on 16 September 2026, 46 days before the check, with no release since in the repository's tags (20). Two releases in the 90 days from 3 August, 0.24.0 on 25 August and 0.24.1, with 0.23.0 on 1 July outside (10 of 20, our batch rule for two). 71 commits on develop since 0.24.1, the last on 30 October, are unreleased. Issues get triage labels, but about a dozen opened in August read needs triage, per the 1 October check, not re-read on 1 November (15 of 25). Current package on PyPI, per the 1 October check (15). CI on three operating systems and supported runtimes stated (10). 20+10+15+15+10 = 70.
Schema & documentation Mistral Moderation API +9
Mistral Moderation API 88
OpenAPI document at docs.mistral.ai/openapi.yaml, per the 1 November reading on the Mistral API listing (25). llms.txt and Markdown twins of every page, re-read on 4 November (10). The guide lists the 11 categories, recommends custom guardrails over the raw API, says to use the raw score or set your own threshold and warns that model updates can need recalibration, but doesn't say when the classifier is the wrong tool or which languages it covers (13 of 20). model and input are typed, input takes a string or an array, and the chat endpoint takes typed messages (12 of 15). Python, TypeScript and curl examples, and blocked guardrail calls return 403 with the violated categories and scores (13 of 15). Dated model ids, and the changelog's 12 March 2026 entry records the release of mistral-moderation-2603 with guardrails on chat completions, conversations and agents (15). 25+10+13+12+13+15 = 88.
NVIDIA NeMo Guardrails 79
Framework reading. Rail configuration is typed in Python and validated on load, and the server speaks the OpenAI chat-completions shape. The repository holds a Fern OpenAPI file, generated at docs build time since 23 October 2026, but no published OpenAPI document for /v1/checks was found in the docs (15 of 25). The docs serve llms.txt at docs.nvidia.com/nemo/guardrails/llms.txt, with a 681-line index of Markdown pages for the latest version and one per release from 0.22.0 (10). The docs describe each rail type and the built-in and third-party rails, and 0.24.0 added IORails, which runs input and output rails without the Colang runtime (15 of 20). YAML configuration with typed models, though Colang 1 and Colang 2 coexist (12 of 15). An examples tree in the repository and per-rail guides, little on error responses (12 of 15). Semver releases and a dated changelog (15). 15+10+15+12+12+15 = 79.
Agent ergonomics Mistral Moderation API +8
Mistral Moderation API 75
Each result is 11 booleans and 11 scores, compact and fixed (20 of 25). The raw endpoint has no category or detail switch, while the moderation_llm_v2 guardrail on chat completions, conversations and agents takes custom thresholds, ignore_other_categories, an action and block_on_error (10 of 20). The error glossary maps status codes to fixes (15 of 20). Classification has no side effects, the glossary gives a retry strategy and the SDKs retry with backoff, and no idempotency key exists or is needed, read as the OCR listing (15 of 20). Two required fields and official SDKs in Python and TypeScript (15). 20+10+15+15+15 = 75.
NVIDIA NeMo Guardrails 67
Framework reading. An OpenAI client pointed at the server needs no code, but each rail set needs a config directory with config.yml and prompts (20 of 25). /v1/checks returns a RailOutcome of allow, block or transform since 0.24.0 (15 of 20). Streaming rails fail closed when an action errors, but error responses aren't documented as such (12 of 20). Checks are stateless, but every LLM-based rail is an extra model call to budget and retry (12 of 20). Python only, many defaults, and two Colang versions to choose between (8 of 15).
Security & auth Mistral Moderation API +8
Mistral Moderation API 70
Read on the same pages as the other Mistral listings. Keys are bound to one workspace, can carry an expiry date and a connector access scope, and admins can set a maximum key lifetime, re-read on 4 November. A key can't be limited to moderation (26 of 30). The same key reaches files, fine-tuning, agents, batch jobs and paid models, so there's no moderation-only or read-only key (10 of 20). A jailbreaking category in the classifier, one score rather than a document-aware injection check (12 of 15). Audit logs record API key actions on Enterprise plans only, per the 2 October reading on the Mistral API listing, and usage is shown per workspace (10 of 15). security.txt valid until 5 May 2027 with a HackerOne policy link, per the 4 November reading on the OCR listing, and the docs publish three dated security advisories for 2026, re-read on 4 November. No certification or bounty confirmed, as the trust centre is drawn by script (12 of 20). 26+10+12+10+12 = 70.
NVIDIA NeMo Guardrails 62
Framework reading. No auth of its own, and SECURITY.md says authentication, authorisation, TLS and rate limiting are the deployer's job. Provider keys come from the environment (10 of 30). Tool-input and tool-output rails can block a tool call, but there's no human approval hook, and the LLM-judged tool_safety_check is only on develop since 29 September 2026 (12 of 20). Jailbreak heuristics and model, injection detection and content-safety rails, documented (15). OpenTelemetry tracing to your own backend, opt-in (12 of 15). Disclosure through NVIDIA PSIRT, no bug bounty, no published advisories, and usage telemetry to NVIDIA on by default with a documented opt-out (13 of 20).
Score by category
| Category | Weight | Mistral Moderation API | NVIDIA NeMo Guardrails | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 75 | NVIDIA NeMo Guardrails +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 79 | Mistral Moderation API +9 |
| Agent ergonomics | 13% | 75 | 67 | Mistral Moderation API +8 |
| Security & auth | 14% | 70 | 62 | Mistral Moderation API +8 |
| Payments & pricing | 10% | 60 | 90 | NVIDIA NeMo Guardrails +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 70 | Mistral Moderation API +13 |
| Transparency & trust | 7% | 80 | 72 | Mistral Moderation API +8 |
| Negative events | ≤15 | -6 | 0 | |
| Total | B 63.1/100 | BB 73.2/100 |
Facts side by side
| Fact | Mistral Moderation API | NVIDIA NeMo Guardrails |
|---|---|---|
| Kind | HTTP API | Agent framework |
| Vendor | Mistral AI | NVIDIA |
| Hosted endpoint | https://api.mistral.ai/v1/moderations | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-03-01 | 2026-09-16 |
| Terms last updated | 2026-09-25 | couldn't be read |
| Privacy policy last updated | 2026-09-03 | no date given |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 769 stars, 8.4M npm/wk, 3.7M PyPI/wk | 7.2k stars, 101k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Mistral Moderation API | NVIDIA NeMo Guardrails |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 Eleven scores, and the best error text is a 403 | 3/5 Typed rail config, but no contract for /v1/checks |
| WardenSecurity auditor | 2/5 A moderation key that also reaches fine-tuning and files | 3/5 No auth by design, and a heartbeat to NVIDIA every 10 minutes |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Mistral Moderation API
Free, on the same key as the rest of the Mistral API, with 11 categories including jailbreaking and PII, and the Experiment plan needs no card. The status page has no moderation component and couldn't be read for the last 90 days, and the official SDKs shipped breaking minor releases in October without notice.
NVIDIA NeMo Guardrails
Apache-2.0, 7,200 stars and nine releases between 9 October 2025 and 16 September 2026. Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default.
Before you call either
Mistral Moderation API
- Use /v1/chat/moderations with the full message list when checking an assistant reply. The raw endpoint has no context
- Read category_scores and set your own threshold per category. The booleans use Mistral's cut-offs
- Pin mistral-moderation-2603. The 2411 model was retired on 30 June 2026
- Pin the SDK version. Minor releases of
mistralaiand@mistralai/mistralaicarry breaking changes - For a Mistral-hosted call, set the moderation_llm_v2 guardrail with block_on_error true and skip the separate request
NVIDIA NeMo Guardrails
- Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
- Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
- Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
- Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
- Put the server behind your own gateway. It has no auth or rate limiting
Questions
Which is better for AI agents, Mistral Moderation API or NVIDIA NeMo Guardrails?
NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Mistral Moderation API's 63.1 (B), and leads in 2 of 7 scored categories. Mistral Moderation API leads on schema & documentation, agent ergonomics, security & auth, maintenance & community and transparency & trust.
Can an agent call Mistral Moderation API and NVIDIA NeMo Guardrails without installing anything?
Mistral Moderation API has a hosted endpoint at https://api.mistral.ai/v1/moderations. No hosted endpoint is listed for NVIDIA NeMo Guardrails.
Are Mistral Moderation API and NVIDIA NeMo Guardrails open source?
No open-source release is listed for Mistral Moderation API. NVIDIA NeMo Guardrails is open source (Apache-2.0).
Other comparisons with Mistral Moderation API or NVIDIA NeMo Guardrails
- Amazon Bedrock Guardrails vs Mistral Moderation API
- Azure AI Content Safety (Prompt Shields) vs Mistral Moderation API
- Cisco AI Defense Inspection API vs Mistral Moderation API
- Google Cloud Model Armor vs Mistral Moderation API
- Granite Guardian vs Mistral Moderation API
- Granite Guardian vs NVIDIA NeMo Guardrails
- Guardrails AI vs Mistral Moderation API
- Lakera Guard (Check Point AI Guardrails) vs Mistral Moderation API
- Llama Guard 4 vs Mistral Moderation API
- Llama Guard 4 vs NVIDIA NeMo Guardrails
- Mistral Moderation API vs OpenAI Guardrails
- Mistral Moderation API vs OpenAI Moderation API
- Mistral Moderation API vs Prisma AIRS AI Runtime Security API
- Mistral Moderation API vs ShieldGemma
- NVIDIA NeMo Guardrails vs OpenAI Moderation API
- NVIDIA NeMo Guardrails vs ShieldGemma
- Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails
- Azure AI Content Safety (Prompt Shields) vs NVIDIA NeMo Guardrails
- Cisco AI Defense Inspection API vs NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs NVIDIA NeMo Guardrails
- Guardrails AI vs NVIDIA NeMo Guardrails
- Lakera Guard (Check Point AI Guardrails) vs NVIDIA NeMo Guardrails
- LlamaFirewall vs NVIDIA NeMo Guardrails
- NVIDIA NeMo Guardrails vs OpenAI Guardrails
- NVIDIA NeMo Guardrails vs Prisma AIRS AI Runtime Security API
- AgentGate vs Mistral Moderation API
- AgentGate vs NVIDIA NeMo Guardrails
- LlamaFirewall vs Mistral Moderation API
- Presidio vs Mistral Moderation API
- Presidio vs NVIDIA NeMo Guardrails
Machine-readable
- This page as Markdown
/compare/mistral-moderation-vs-nemo-guardrails.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mistral-moderation.json·/api/v1/tools/nemo-guardrails.json - From a terminal
anchor compare mistral-moderation nemo-guardrails(the CLI) - Over MCP
compare_tools {"a": "mistral-moderation", "b": "nemo-guardrails"}at/mcp, no key