Amazon Bedrock Guardrails vs OpenAI Moderation API

Amazon Bedrock Guardrails

ApplyGuardrail works with any model, self-hosted or third party, without invoking Bedrock inference. Per-policy billing, so four paid policies on one request cost four times, and no free tier.

OpenAI Moderation API

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

Amazon Bedrock Guardrails

1. Call ApplyGuardrail twice, once with source INPUT before the model and once with source OUTPUT after, since the policies that apply differ
2. Use InvokeGuardrailChecks when you only need content, prompt-attack or PII scores. It needs no guardrail id and runs in detect-only mode
3. Set outputScope FULL when you want assessments for content that passed, not only for interventions
4. Budget in text units of 1,000 characters per policy. A 5,000-character tool result is five units on every paid policy
5. Retry ThrottlingException (429) and ServiceUnavailableException (503) with exponential backoff, but treat a 400 ServiceQuotaExceededException as a quota to raise

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