Head to head · Content moderation · October 2026 research run

Azure AI Content Safety (Prompt Shields) vs Mistral Moderation API

Azure AI Content Safety (Prompt Shields) scores 68 (B) on agent readiness against Mistral Moderation API's 63.1 (B), and leads in 4 of 7 scored categories. Mistral Moderation API leads on schema & documentation, payments & pricing and maintenance & community. Both do content moderation.

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

Which one, for what

Azure AI Content Safety (Prompt Shields) B

Best for An agent on Azure that retrieves documents and needs indirect-injection checks next to harm-category moderation.

Ahead on

  • Reliability, 75 against 43
  • Security & auth, 86 against 70

Also in its favour

  • No incidents deducted, where Mistral Moderation API loses 6 points for them

Watch for

Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call

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 74
  • Payments & pricing, 60 against 23
  • Maintenance & community, 83 against 35

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 +48

Azure AI Content Safety (Prompt Shields) 35

Read as a closed service with official SDKs, from Microsoft's dated sources as the other Azure listings are. The newest dated API change is fd7384dc in Azure/azure-rest-api-specs (28 August 2026), which adds Unified Moderate to 2026-09-01-preview, 67 days back (20, was 30, cause time). Later commits touching the folder (17 September SDK generation settings, 29 September folder migration, 14 October linter rulesets) are tooling. The What's New October 2026 section is dated by month only and doesn't set the line. SDK pre-releases on 14 September (Python 1.1.0b1, Java 1.1.0-beta.1) and 18 September (.NET 1.1.0-beta.1, and @azure/ai-content-safety 1.0.0-beta.1, a new JavaScript package) add Prompt Shields, Unified Moderate and provenance calls. Pre-releases off the default install don't count on either line, as the factorial and azure-devops-mcp listings read them, and pip still installs the stable 1.0.0. In the 90 days from 5 August the 28 August spec change counts once. Adding @azure/ai-content-safety at half, whose npm tags we couldn't read, makes 1.5, still under three (0). Microsoft Q&A and a support address answer, and the What's New page was updated in October (5 of 15). The stable SDKs still lag the service, Python 1.0.0 from December 2023 and @azure-rest/ai-content-safety 1.0.1 from January 2025, neither with a Prompt Shields helper (5 of 15). Stable packages unchanged for 35 and 22 months (5 of 10). 20 + 0 + 5 + 5 + 5 = 35.

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 Mistral Moderation API +37

Azure AI Content Safety (Prompt Shields) 23

No x402, MPP or L402 (0). Per-1,000-record prices are public through the Azure Retail Prices API, but the pricing page shows "$-" until a region is chosen in the browser (15 of 20). F0 gives 5,000 free text records and 5,000 images a month, but it needs an Azure subscription and an Azure account needs a card (0). A person signs up and creates the resource in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

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.

Reliability Azure AI Content Safety (Prompt Shields) +32

Azure AI Content Safety (Prompt Shields) 75

Azure status page with a post-incident review history (20). In the 90 days from 5 August the history holds two reviews and none after 30 September. The 29 September review covers intermittent failures and latency for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, one region and a share of requests, so partial and minor, as the Azure Speech, Translator, Document Intelligence and Foundry fine-tuning listings read it. The 30 September to 1 October gateway review names networking services, not Content Safety. The 23 July West US review counted on 1 October has left the window. Minor only (20, was 10). Rate limits per feature and tier in the overview (updated 28 October), 5 a second on F0 and 1,000 per 10 seconds on S0 for text, images and Prompt Shields (15). No 429 or backoff guidance in the Content Safety docs (0). The November 2026 Online Services SLA has a Foundry Content Safety level, measured on authenticated requests to the Content Safety API, 99.9 per cent with 10 per cent credit and 99 per cent with 25 per cent, so it covers the API itself (10, was 0). Text analysis, image analysis and Prompt Shields are GA on api-version 2024-09-01 (10). 20 + 20 + 15 + 0 + 10 + 10 = 75.

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.

Security & auth Azure AI Content Safety (Prompt Shields) +16

Azure AI Content Safety (Prompt Shields) 86

Microsoft Entra ID tokens with RBAC, or two resource keys that can be regenerated in turn (30). RBAC can limit a caller, but a resource key also reaches the blocklist write and delete operations, with no confirmation step (15 of 20). Prompt Shields detects user-prompt and document attacks, and the docs describe Spotlighting for third-party content, in preview (15). The Foundry Tools diagnostic logging page describes Audit and RequestResponse logs through Azure Monitor for Cognitive Services resources once the owner adds a diagnostic setting, as the Document Intelligence listing reads it. We didn't confirm the fields for Content Safety (12, was 0). Coordinated disclosure policy and MSRC bounty programmes linked from security.txt, but microsoft.com's security.txt passed its Expires date on 23 September 2026 and still carries it on 3 November (4 of 5), bounty (5), SOC or ISO coverage for Content Safety by name not confirmed (0), MSRC publishes advisories (5), so 14 of 20. An MSRC affected-product search on 3 November finds no CVE naming Content Safety. The 2026 Azure AI Foundry CVEs name Foundry, not this service, so no deduction, as on the Speech, Translator and Document Intelligence listings. 30 + 15 + 15 + 12 + 14 = 86.

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.

Schema & documentation Mistral Moderation API +14

Azure AI Content Safety (Prompt Shields) 74

Public OpenAPI (Swagger) documents in Azure/azure-rest-api-specs, with stable 2024-09-01 and previews up to 2026-09-01-preview, error schemas and examples on all 15 operations (25). learn.microsoft.com has no llms.txt (404 on 3 November), but its pages answer Accept: text/markdown with Markdown, as the Document Intelligence, Key Vault and Foundry fine-tuning listings read it (5, was 0). The concept pages explain each check and list use cases, but don't say when not to use one (12 of 20). Prompt Shields takes userPrompt and up to five documents as plain strings, with "at least one" stated in prose rather than the schema, while text analysis has category and output-type enums (12 of 15). Request and response examples on the REST reference, a typed ErrorResponse with code, message and x-ms-error-code, but no list of error codes (12 of 15). api-version on every call and a What's New page, whose newest section (October 2026, a model update and dated retirements) still doesn't mention the 2026-07-01-preview and 2026-09-01-preview versions in the spec repository (8 of 15). 25 + 5 + 12 + 12 + 12 + 8 = 74.

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.

Score by category

CategoryWeightAzure AI Content Safety (Prompt Shields)Mistral Moderation APIEdge
Reliability16%7543Azure AI Content Safety (Prompt Shields) +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7488Mistral Moderation API +14
Agent ergonomics13%7875Azure AI Content Safety (Prompt Shields) +3
Security & auth14%8670Azure AI Content Safety (Prompt Shields) +16
Payments & pricing10%2360Mistral Moderation API +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3583Mistral Moderation API +48
Transparency & trust7%8380Azure AI Content Safety (Prompt Shields) +3
Negative events≤150-6
TotalB 68/100B 63.1/100

Facts side by side

FactAzure AI Content Safety (Prompt Shields)Mistral Moderation API
KindHTTP APIHTTP API
VendorMicrosoftMistral AI
Hosted endpointhttps://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompthttps://api.mistral.ai/v1/moderations
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-282026-03-01
Terms last updatedcouldn't be read2026-09-25
Privacy policy last updated2026-09-012026-09-03
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity17k npm/wk, 218k PyPI/wk769 stars, 8.4M npm/wk, 3.7M PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Azure AI Content Safety (Prompt Shields)

Prompt Shields checks up to five retrieved documents for indirect injection, not only the user prompt, and the API has its own 99.9 per cent SLA level. Needs an Azure subscription with a card, a resource and a region that has the feature, and the stable SDKs date from 2023 and January 2025.

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

Azure AI Content Safety (Prompt Shields)

  1. Send retrieved pages and tool results in the documents array of shieldPrompt, not in userPrompt, so document attacks are reported separately
  2. Call text:shieldPrompt over REST with api-version=2024-09-01. The stable Python SDK 1.0.0 has no method for it, only the 1.1.0b1 pre-release
  3. Keep each request under 10,000 characters across prompt and documents, and split long tool results
  4. Create the resource in a region that lists Prompt Shields, since not every region has it
  5. On F0 you get 5 requests a second. Queue checks or move to S0 before load testing
  6. Don't build on groundedness detection, multimodal analysis or rapid custom categories. They retire on 30 April 2027

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, Azure AI Content Safety (Prompt Shields) or Mistral Moderation API?

Azure AI Content Safety (Prompt Shields) scores 68 (B) on agent readiness against Mistral Moderation API's 63.1 (B), and leads in 4 of 7 scored categories. Mistral Moderation API leads on schema & documentation, payments & pricing and maintenance & community.

Do Azure AI Content Safety (Prompt Shields) and Mistral Moderation API need an API key?

Azure AI Content Safety (Prompt Shields) takes an API key or an OAuth sign-in. Mistral Moderation API needs an API key.

Can an agent call Azure AI Content Safety (Prompt Shields) and Mistral Moderation API without installing anything?

Yes. Azure AI Content Safety (Prompt Shields) has a hosted endpoint at https://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompt and Mistral Moderation API at https://api.mistral.ai/v1/moderations.

Other comparisons with Azure AI Content Safety (Prompt Shields) 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.