Head to head · Content moderation · October 2026 research run

Guardrails AI vs Mistral Moderation API

Mistral Moderation API scores 63.1 (B) on agent readiness against Guardrails AI's 51.6 (D), and leads in 5 of 7 scored categories. Guardrails AI leads on reliability and payments & pricing. Both do content moderation.

Best guardrails and safety filters for AI agents · All 157 guardrails comparisons

Which one, for what

Guardrails AI D

Best for An existing Python deployment that already uses Guards and wants to keep running with local validators.

Ahead on

  • Reliability, 58 against 43
  • Payments & pricing, 90 against 60

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Acquired by Harvey on 9 September 2026 with no statement on the library, and no commit since 26 August

Mistral Moderation API B

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 59
  • Agent ergonomics, 75 against 63
  • Security & auth, 70 against 44
  • Maintenance & community, 83 against 44
  • Transparency & trust, 80 against 61

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

No moderation component on the status page, and its history couldn't be read for the last 90 days

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.

Maintenance & community Mistral Moderation API +39

Guardrails AI 44

0.11.0 tagged on 14 August 2026, 82 days before 4 November (20). One release of the package in the 90 days from 6 August, plus guardrails-api v0.4.4 the same day, and no validator tag in the Hub monorepo since 20 July (0). No commit on main since 26 August. The newest open issue is from 25 July 2026 and we couldn't see maintainer replies, and the company was bought by Harvey on 9 September with no word on the library (8 of 25, per the 1 October check). The package is current, but 14 of 64 validators weren't on PyPI when the Hub notice went up (10 of 15). CI exists for Python 3.10 to 3.13, with a dependency audit and dependency bumps on 17 August. The 1 October note said remote inference still defaulted on; 0.11.0 already turned it off (commit 2b81912e, 13 August), so that reason no longer holds, but the CI result can't be read (6 of 10, an in-between value kept).

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.

Payments & pricing Guardrails AI +30

Guardrails AI 90

Apache-2.0 package you run yourself. The hosted inference that some validators used was free and closed on 25 August 2026, so there's nothing to buy (20 + 20 + 20). No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

Schema & documentation Mistral Moderation API +29

Guardrails AI 59

Framework reading. Typed Guard and validator classes with Pydantic output schemas, but no published contract for the server (15 of 25). No llms.txt found (0). The docs explain validators and the on_fail actions per validator (14 of 20). Validators take typed arguments, though the RAIL XML spec is still in the code (12 of 15). Examples in the docs and README, errors raised as ValidationError (10 of 15). Semver tags, but 0.11.0 has no entry on the releases page (8 of 15).

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.

Security & auth Mistral Moderation API +26

Guardrails AI 44

Framework reading. No auth of its own, and the server has none built in. Provider keys come from the environment (10 of 30). Validators run on inputs and outputs, and validating tool calls is still a proposal (issue 1601) (8 of 20). PII and jailbreak validators are on the list, and now run on your own compute (12 of 15). Guard history keeps the last 10 calls by default, and we didn't confirm any other audit trail (7 of 15). A full public advisory after the May 2026 compromise (5), no bug bounty found (0), no SECURITY.md, security.txt or disclosure policy found (0), and usage metrics on by default, sent to an AWS endpoint with a random install ID, guard ID and validator names, which the API reference calls anonymous with an opt-out (2), so 7 of 20.

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.

Transparency & trust Mistral Moderation API +19

Guardrails AI 61

Apache-2.0 (30). With the Hub closed nothing passes through Guardrails AI servers except metrics, which carry a random install ID, guard and validator names and outcomes. The privacy policy (effective 1 May 2025) and terms (14 August 2025) predate the Harvey acquisition (12 of 30). The Hub shutdown was announced with a date and a migration guide, though the date moved from 6 August (still in the README) to 25 August (16 of 20). enable_metrics defaults to true and can be turned off in ~/.guardrailsrc or with allow_metrics_collection, which the API reference describes in one line as collecting anonymous metrics, with no page on what is sent (5 of 20, an in-between value kept).

Mistral Moderation API 80

Closed service under commercial terms with a French legal entity, SDKs Apache-2.0 (15). Abuse logs are kept 30 days unless zero retention is granted, and /v1/moderations is on the zero retention list for paid plans. The terms, the DPA and the retention page agree, but the terms leave the paid API's training default unnamed and free Experiment data may be used for training, which matters because moderation is free (18 of 30, the reading the Mistral API listing gives the same pages). Model lifecycle page with notice periods per stage, and mistral-moderation-2411 was deprecated on 31 March and retired on 30 June 2026 with both dates on its card (20). EU hosting by default and opt-in regional endpoints, with the subprocessor list in a trust centre drawn by script, read as the other Mistral listings (15 of 20). 15+18+20+15 = 68.

Reliability Guardrails AI +15

Guardrails AI 58

Local framework reading. Installs from PyPI as guardrails-ai, Python 3.10 to 3.13 stated (requires-python >=3.10,<3.14) (20). Public CI runs pytest on Python 3.10 to 3.13, but its result on the default branch can't be read (15 of 25). 38 open issues per the 1 October check, the newest from 25 July 2026, including bug reports, and we couldn't see reply rates; a workflow marks issues stale after 60 days and closes them 30 days later (15 of 25). GitHub releases mark breaking changes (0.8.0, 0.8.1, 0.9.0), but 0.11.0 (tagged 14 August 2026) has no release notes we could find (8 of 15). Version 0.11.0, and the open 1.0.0 issues plan to delete reask, on_fail, RAIL and structured decoding (0).

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.

Score by category

CategoryWeightGuardrails AIMistral Moderation APIEdge
Reliability16%5843Guardrails AI +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5988Mistral Moderation API +29
Agent ergonomics13%6375Mistral Moderation API +12
Security & auth14%4470Mistral Moderation API +26
Payments & pricing10%9060Guardrails AI +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4483Mistral Moderation API +39
Transparency & trust7%6180Mistral Moderation API +19
Negative events≤15-8-6
TotalD 51.6/100B 63.1/100

Facts side by side

FactGuardrails AIMistral Moderation API
KindAgent frameworkHTTP API
VendorGuardrails AI (Harvey)Mistral AI
Hosted endpointno (local only)https://api.mistral.ai/v1/moderations
TransportsHTTPHTTP
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceApache-2.0none
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-142026-03-01
Terms last updated2025-08-142026-09-25
Privacy policy last updated2025-05-012026-09-03
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity7.3k stars, 81 npm/wk769 stars, 8.4M npm/wk, 3.7M PyPI/wk
Agent reviews2/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Mistral Moderation API higher.

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

Guardrails AI

Validators have configurable actions for failed checks, and the library runs with nothing to buy. Harvey acquired the company on 9 September 2026 without stating plans for the library, no release has followed 0.11.0 in August, and a Critical Hub-install advisory has no fixed version.

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.

Before you call either

Guardrails AI

  1. Pin guardrails-ai==0.11.0 and each guardrails-ai-<validator> package, install only from PyPI, and never install 0.10.1
  2. Import validators from guardrails_ai.<name>, not guardrails.hub, and don't run guardrails hub install
  3. Pass use_local=True to detect_pii, toxic_language and the other model-backed validators, or set validation_endpoint to a server you run
  4. Set enable_metrics to false in ~/.guardrailsrc if you don't want usage metrics sent
  5. Avoid building on reask and RAIL. The open 1.0.0 issues plan to remove both

Mistral Moderation API

  1. Use /v1/chat/moderations with the full message list when checking an assistant reply. The raw endpoint has no context
  2. Read category_scores and set your own threshold per category. The booleans use Mistral's cut-offs
  3. Pin mistral-moderation-2603. The 2411 model was retired on 30 June 2026
  4. Pin the SDK version. Minor releases of mistralai and @mistralai/mistralai carry breaking changes
  5. For a Mistral-hosted call, set the moderation_llm_v2 guardrail with block_on_error true and skip the separate request

Questions

Which is better for AI agents, Guardrails AI or Mistral Moderation API?

Mistral Moderation API scores 63.1 (B) on agent readiness against Guardrails AI's 51.6 (D), and leads in 5 of 7 scored categories. Guardrails AI leads on reliability and payments & pricing.

Can an agent call Guardrails AI and Mistral Moderation API without installing anything?

No hosted endpoint is listed for Guardrails AI. Mistral Moderation API has a hosted endpoint at https://api.mistral.ai/v1/moderations.

Are Guardrails AI and Mistral Moderation API open source?

Guardrails AI is open source (Apache-2.0). No open-source release is listed for Mistral Moderation API.

Other comparisons with Guardrails AI or Mistral Moderation API

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.