Head to head · Content moderation · October 2026 research run

Lakera Guard (Check Point AI Guardrails) vs OpenAI Moderation API

OpenAI Moderation API scores 74 (BB) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in 6 of 7 scored categories. Lakera Guard (Check Point AI Guardrails) leads on reliability. Both do content moderation.

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

Which one, for what

Lakera Guard (Check Point AI Guardrails) B

Best for An agent that wants one hosted call to screen user input, tool calls and tool results for injection in the OpenAI message format.

Ahead on

  • Reliability, 70 against 65

Also in its favour

  • Free to start without a card

Watch for

Prompts and outputs are stored for the dashboard by default

OpenAI Moderation API BB

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

Ahead on

  • Security & auth, 95 against 83
  • Payments & pricing, 45 against 23
  • Maintenance & community, 47 against 21
  • Transparency & trust, 90 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.0 against 3.5 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.

Transparency & trust OpenAI Moderation API +28

Lakera Guard (Check Point AI Guardrails) 62

Closed service. The footer terms link now renders as text, Check Point's website terms naming Check Point Software Technologies Ltd and its affiliates, with disputes before the courts of Tel Aviv, and product use governed by the Check Point End User License Agreement (15 of 30; was 10 when the page couldn't be read). Prompts and outputs are stored for the dashboard by default and admins can switch it off, retention controls are Enterprise-only, the trust centre says data is deleted on request, and no retention period is published for Community (15 of 30). No deprecation policy or dated notices found; the retired v1-beta policy endpoints say only that they were retired with Policies V2 (0). Storage region fixed at organisation creation (EU by default), regional EU, US and Singapore hosts, and a sub-processor list on checkpoint.com (18 of 20). 15+15+0+18 = 48.

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.

Maintenance & community OpenAI Moderation API +26

Lakera Guard (Check Point AI Guardrails) 21

Every dated source of the vendor's own was looked for, in the changelog (container releases through 2.0.493 on 2 April 2026, product entries on 10 April, 1 and 8 June and 26 October 2026), no official Guard SDK or MCP package. The newest entry, "Request Latency Percentiles" on 26 October 2026, adds a chart of Guard API request latency to the dashboard's Analytics page and changes nothing the API takes or returns, so it isn't read as an API change. The last API change is still Enhanced Breakdown Response on 8 June 2026, 149 days back (10). One dated entry since 6 August (0). Public changelog and Check Point support, no public issue tracker (8 of 15). No official SDK packages for the Guard API; the red-teaming SDK in the docs is another product (0). Self-hosted container releases on the stable tag every few weeks until 2.0.493 on 2 April 2026 (3 of 10). 10+0+8+0+3 = 21.

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.

Payments & pricing OpenAI Moderation API +22

Lakera Guard (Check Point AI Guardrails) 23

No x402, MPP or L402 (0). The Community limit of 10,000 requests a month is public, but there's no price above it, and Enterprise is by sales; www.lakera.ai/pricing redirects to the platform's script-drawn pricing page (5 of 20, our call for a published free plan with no prices). Community is self-serve, and the 30 September check found no card step, which we couldn't repeat (10 of 20). A person signs up on platform.lakera.ai and makes the key (0). 0+5+10+0 = 15. 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.

Security & auth OpenAI Moderation API +12

Lakera Guard (Check Point AI Guardrails) 83

Bearer API keys made on the dashboard. The API reference now says keys carry one of two access scopes chosen at creation, read and write (the default, and the scope of every older key) or read only, where write endpoints return 403. No expiry or rotation documented (24 of 30; was 20). Dashboard roles are User, Admin and No access, and a read-only key can be given to log shippers and dashboards so it can't change policies or projects (14 of 20; was 10). The service is a prompt-attack detector that also screens tool calls and tool results in the same request (15). Every screening request is logged with its prompt and output in the dashboard by default, and logs can be exported to S3 for a SIEM (15). SOC 2 Type II and ISO 27001:2022 on the trust centre per the 1 October check. Check Point publishes a vulnerability disclosure policy covering its products and owned domains, with acknowledgements and no monetary rewards, and posts security advisories in public. No security.txt on lakera.ai or checkpoint.com (both 404 on 4 November), no bug bounty, and no advisory touching AI Guardrails found (15 of 20; was 5 with no disclosure policy found). 24+14+15+15+15 = 83.

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.

Reliability Lakera Guard (Check Point AI Guardrails) +5

Lakera Guard (Check Point AI Guardrails) 70

status.checkpoint.com still lists Check Point AI Security (Lakera Guard) with Lakera Guard Platform and Lakera Guard API components for the EU, US and APAC (20). Its history feed, read on 4 November, has 25 entries from 27 June to 2 November 2026, and none in the window from 6 August touches the Guard components (the 25 October "Service Down due to incident" page names Check Point Mobile Security only), so a clean record (30). No rate-limit numbers published for Community or Enterprise (0). The API reference now documents 429 as "Too many requests, or the Guard API is temporarily overloaded. The request was not screened. Retry it after a short delay", and 503 with "Retry the request", with no Retry-After header (10 of 15; was 5). No SLA found (0). /v2/guard is GA (10). 20+30+0+10+0+10 = 70.

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

CategoryWeightLakera Guard (Check Point AI Guardrails)OpenAI Moderation APIEdge
Reliability16%7065Lakera Guard (Check Point AI Guardrails) +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9092OpenAI Moderation API +2
Agent ergonomics13%8385OpenAI Moderation API +2
Security & auth14%8395OpenAI Moderation API +12
Payments & pricing10%2345OpenAI Moderation API +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2147OpenAI Moderation API +26
Transparency & trust7%6290OpenAI Moderation API +28
Negative events≤150-2
TotalB 66.8/100BB 74/100

Facts side by side

FactLakera Guard (Check Point AI Guardrails)OpenAI Moderation API
KindHTTP APIHTTP API
VendorCheck PointOpenAI
Hosted endpointhttps://api.lakera.ai/v2/guardhttps://api.openai.com/v1/moderations
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFree
x402nono
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-06-082026-06-04
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-06-01couldn't be read
Customer content may train modelsyescouldn'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 waivernot found in the textcouldn't be read
Popularitynone31k stars
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates 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

Lakera Guard (Check Point AI Guardrails)

One hosted call screens user input, tool calls and tool results in the OpenAI message format, and the reference says which errors to retry. Prompts and outputs are stored for the dashboard by default, there are no prices above the free tier or published rate limits, and the changelog had one entry between June and November 2026.

OpenAI Moderation API

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

Before you call either

Lakera Guard (Check Point AI Guardrails)

  1. Start the project in Detect mode and calibrate before Enforce. In Detect mode flagged is always false
  2. Send the whole conversation, but expect only the last user, assistant or tool turn to be scored
  3. Ask for breakdown=true and treat the confidence levels as a dial, not a boolean
  4. Turn off prompt logging in General Settings if the dashboard shouldn't hold user content
  5. Pin eu.api.lakera.ai or us.api.lakera.ai rather than api.lakera.ai when residency matters
  6. Retry 429 and 503 after a short delay; don't resend a 422 unchanged

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, Lakera Guard (Check Point AI Guardrails) or OpenAI Moderation API?

OpenAI Moderation API scores 74 (BB) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in 6 of 7 scored categories. Lakera Guard (Check Point AI Guardrails) leads on reliability.

Do Lakera Guard (Check Point AI Guardrails) and OpenAI Moderation API need an API key?

Both need an API key.

Can an agent call Lakera Guard (Check Point AI Guardrails) and OpenAI Moderation API without installing anything?

Yes. Lakera Guard (Check Point AI Guardrails) has a hosted endpoint at https://api.lakera.ai/v2/guard and OpenAI Moderation API at https://api.openai.com/v1/moderations.

Other comparisons with Lakera Guard (Check Point AI Guardrails) 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.