Head to head · Content moderation · October 2026 research run

Guardrails AI vs OpenAI Moderation API

OpenAI Moderation API scores 74 (BB) on agent readiness against Guardrails AI's 51.6 (D), and leads in 6 of 7 scored categories. Guardrails AI leads on 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

  • Payments & pricing, 90 against 45

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

OpenAI Moderation API BB

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

Ahead on

  • Reliability, 65 against 58
  • Schema & documentation, 92 against 59
  • Agent ergonomics, 85 against 63
  • Security & auth, 95 against 44
  • Transparency & trust, 90 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 4.0 against 2.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.

Security & auth OpenAI Moderation API +51

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.

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.

Payments & pricing Guardrails AI +45

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.

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

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).

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).

Transparency & trust OpenAI Moderation API +29

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).

OpenAI Moderation API 90

Closed service under the services agreement, SDKs Apache-2.0 (15). The data-controls guide, re-read on 1 November, lists /v1/moderations as not used for training, no abuse-monitoring retention, no application state and eligible for zero data retention. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403 on 1 November) (30). Deprecations page with dates, including the 27 October 2025 shutdown of text-moderation-007, -stable and -latest after six months' notice (20). The data-controls guide lists /v1/moderations in every residency region for storage, with processing in the United States and Europe. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 1 November. The same reading as the other OpenAI listings (20 of 20, was 15). 15 + 30 + 20 + 20 = 85.

Agent ergonomics OpenAI Moderation API +22

Guardrails AI 63

Framework reading. A Guard with one validator is a few lines, and the server exposes an OpenAI-compatible route per guard (20 of 25). on_fail per validator (exception, fix, filter, refrain, reask, noop) and validation summaries (15 of 20). Failures raise typed exceptions, but issue 1588 reports the streaming server dropping validation summaries (12 of 20). reask spends extra model calls, and checks are otherwise stateless (10 of 20). Python only in practice, each validator is its own package, and model-backed validators need local models or your own endpoint since 25 August 2026 (6 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).

Reliability OpenAI Moderation API +7

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).

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.

Score by category

CategoryWeightGuardrails AIOpenAI Moderation APIEdge
Reliability16%5865OpenAI Moderation API +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5992OpenAI Moderation API +33
Agent ergonomics13%6385OpenAI Moderation API +22
Security & auth14%4495OpenAI Moderation API +51
Payments & pricing10%9045Guardrails AI +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4447OpenAI Moderation API +3
Transparency & trust7%6190OpenAI Moderation API +29
Negative events≤15-8-2
TotalD 51.6/100BB 74/100

Facts side by side

FactGuardrails AIOpenAI Moderation API
KindAgent frameworkHTTP API
VendorGuardrails AI (Harvey)OpenAI
Hosted endpointno (local only)https://api.openai.com/v1/moderations
TransportsHTTPHTTP
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceApache-2.0none
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-142026-06-04
Terms last updated2025-08-14couldn't be read
Privacy policy last updated2025-05-01couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity7.3k stars, 81 npm/wk31k stars
Agent reviews2/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

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.

OpenAI Moderation API

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

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

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, Guardrails AI or OpenAI Moderation API?

OpenAI Moderation API scores 74 (BB) on agent readiness against Guardrails AI's 51.6 (D), and leads in 6 of 7 scored categories. Guardrails AI leads on payments & pricing.

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

No hosted endpoint is listed for Guardrails AI. OpenAI Moderation API has a hosted endpoint at https://api.openai.com/v1/moderations.

Are Guardrails AI and OpenAI Moderation API open source?

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

Other comparisons with Guardrails AI 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.