Head to head · Content moderation · October 2026 research run

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

OpenAI Moderation API scores 74 (BB) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 6 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on reliability. 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 65

Watch for

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

OpenAI Moderation API BB

Best for A free harm-category filter for an agent already on OpenAI.

Ahead on

  • Schema & documentation, 92 against 74
  • Agent ergonomics, 85 against 78
  • Security & auth, 95 against 86
  • Payments & pricing, 45 against 23
  • Maintenance & community, 47 against 35
  • Transparency & trust, 90 against 83

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

No prompt-injection, jailbreak or PII detection

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.

Payments & pricing OpenAI Moderation API +22

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.

OpenAI Moderation API 45

No x402, MPP or L402 (0). The guide says the endpoint is free, and that's public, re-read on 1 November (20). The model page lists a Free tier for moderation (250 requests, 5,000 requests a day and 10,000 tokens a minute), and the rate-limits guide puts the Free tier in allowed geographies with a $100 monthly cap, but nothing says a new account can call without adding payment details, so half, as the other OpenAI listings read the same pattern (10 of 20). A person signs up in a browser and makes the key (0). 0+20+10+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation OpenAI Moderation API +18

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.

OpenAI Moderation API 92

OpenAPI document in openai/openai-openapi covering /v1/moderations (25). llms.txt at developers.openai.com (10). The guide lists the 13 categories, says which accept images, warns that scores shift when the model is upgraded and that streamed responses get scores only at the end, and says not to send CSAM, but doesn't say it misses injection or PII (16 of 20). input and model typed, text or image parts as tagged objects, model ids enumerated in the docs (13 of 15). Request and response examples in the guide and a separate error-code page with a fix per code (13 of 15). Dated snapshot omni-moderation-2024-09-26 and a dated changelog (15).

Maintenance & community OpenAI Moderation API +12

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.

OpenAI Moderation API 47

The newest moderation change is still the moderation object on Responses and Chat Completions in the changelog entry of 4 June 2026, 150 days before 1 November, and the deprecations page has nothing on moderation since the text-moderation shutdown of 27 October 2025, re-read on 1 November (10). No moderation entries in the 90 days to 1 November, though the changelog has 42 dated entries in that time (0). Dated changelog several times a month and a help centre, nothing moderation-specific since June (12 of 15). Current official SDKs, openai-python v3.42.0 and openai-node v7.47.0 are the newest tags on 1 November (15). SDKs generated from the OpenAPI spec, Python 3.10 to 3.14 (10). 10+0+12+15+10 = 47.

Reliability Azure AI Content Safety (Prompt Shields) +10

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.

OpenAI Moderation API 65

status.openai.com has a Moderations component with 90 days of history (20). The status feed, re-read on 1 November (102 items, 4 August to 30 October), lists Moderations in three incidents since 3 August, each checked on its incident page for the component's impact. Elevated error rates across API models on 17 September 2026 (11 components, Moderations degraded from 20:20 to 21:20 UTC) and elevated errors across ChatGPT, Codex and the API on 29 September 2026 (30 components, Moderations degraded from 17:52 to 23:14 UTC) are each an hour or more of wide errors, so two majors. Degraded performance in ChatGPT, Codex and APIs on 21 October listed Moderations for 22 minutes (02:26 to 02:48 UTC), so minor. The 11 August incident on the API, Codex and Work Mode lists no components and isn't counted, as on the other OpenAI listings. Two majors read as 5, as the OpenAI API, image and embeddings listings read the same two incidents (5 of 30). Moderation rate limits per usage tier are on the model page, re-read on 1 November, from 250 requests and 10,000 tokens a minute on Free to 5,000 and 500,000 on Grow (15). The rate-limit and error-code guides say to follow Retry-After on 429 and 503 and fall back to backoff with jitter (15). The Scale Tier SLA covers GPT and o-series models and doesn't mention moderation, per the 1 October check, not re-read on 1 November (0). omni-moderation is GA (10). 20+5+15+15+0+10 = 65.

Security & auth OpenAI Moderation API +9

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.

OpenAI Moderation API 95

Project keys with Restricted and Read-only modes that set None, Read or Write per endpoint, and service-account keys (30). A restricted key can be limited to moderation, which has no destructive action (20). Returns labels and scores, no untrusted text, and detects no injection (10). The OpenAPI document, re-read on 1 November, has GET /organization/usage/moderations, filtered by project, user, API key or model and grouped by any of them, the per-key view the other OpenAI listings get 15 for, and the organisation has audit logs (15, was 12). A signed security.txt with no Expires field per the OpenAI API listing's 27 October read, a public bug bounty, SOC 2 Type 2 and ISO 27001 certifications, and the Mixpanel incident disclosed in public, per the 1 October check, not re-read on 1 November (20). 30+20+10+15+20 = 95.

Agent ergonomics OpenAI Moderation API +7

Azure AI Content Safety (Prompt Shields) 78

Prompt Shields answers one boolean per prompt and per document, and text analysis returns four or eight severity levels by choice (20 of 25). Categories, output type and haltOnBlocklistHit are set per request (20). Errors carry a code and message in a standard Azure shape, but the codes aren't documented per operation (15 of 20). Checks have no side effects, but there's no retry guidance (15 of 20). Few required fields, but the Python SDK is 1.0.0 from 12 December 2023 with no Prompt Shields method, and the JavaScript package is a generic REST client, 1.0.1 from January 2025 (8 of 15).

OpenAI Moderation API 85

A fixed response of flagged, 13 category booleans, 13 scores and the input types each category used, with no field selection (20 of 25). Arrays of inputs in one call, and since 4 June 2026 a moderation object on Responses and Chat Completions returns scores with the generation, but no per-request category choice (10 of 20). The error-code page gives each 401, 403, 429, 500 and 503 a cause and a fix (20). Classification has no side effects and the docs give Retry-After and backoff guidance (20). One required field and official SDKs in Python, JavaScript and other languages (15).

Score by category

CategoryWeightAzure AI Content Safety (Prompt Shields)OpenAI Moderation APIEdge
Reliability16%7565Azure AI Content Safety (Prompt Shields) +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7492OpenAI Moderation API +18
Agent ergonomics13%7885OpenAI Moderation API +7
Security & auth14%8695OpenAI Moderation API +9
Payments & pricing10%2345OpenAI Moderation API +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3547OpenAI Moderation API +12
Transparency & trust7%8390OpenAI Moderation API +7
Negative events≤150-2
TotalB 68/100BB 74/100

Facts side by side

FactAzure AI Content Safety (Prompt Shields)OpenAI Moderation API
KindHTTP APIHTTP API
VendorMicrosoftOpenAI
Hosted endpointhttps://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompthttps://api.openai.com/v1/moderations
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-282026-06-04
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updated2026-09-01couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularity17k npm/wk, 218k PyPI/wk31k stars
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate OpenAI 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

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.

OpenAI Moderation API

Free, on any OpenAI project key. No prompt-injection, jailbreak or PII detection.

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

OpenAI Moderation API

  1. Read category_scores rather than flagged alone. The default thresholds are OpenAI's
  2. Pin omni-moderation-2024-09-26 if the scores feed a decision you audit. The latest alias will move
  3. Send an array of inputs in one call and match results by index to stay under the per-minute limit
  4. Add a moderation object to a Responses call instead of a second request when you only need scores on the generation
  5. Pair it with a separate injection detector. A clean result says nothing about a hidden instruction in a tool result

Questions

Which is better for AI agents, Azure AI Content Safety (Prompt Shields) or OpenAI Moderation API?

OpenAI Moderation API scores 74 (BB) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 6 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on reliability.

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

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

Can an agent call Azure AI Content Safety (Prompt Shields) and OpenAI 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 OpenAI Moderation API at https://api.openai.com/v1/moderations.

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