Skip to main content
POST /api/v2/moderation/check Runs the content-moderation engine against the supplied text without blocking, returning structured findings so a buyer agent can validate input before submitting it to a blocking surface. Mirrors the engine behind POST /campaigns brief screening — wouldBlock: true predicts a 422 on the real call.

Request

Parameters

Response

A blocking example:
passed is true only when no patterns matched. wouldBlock is true when at least one finding would trigger a 422 on a blocking surface. findings reports both blocking and non-blocking matches, so medium-severity signals are visible even when wouldBlock is false. Each finding carries a category, a severity (low, medium, high, critical), and a suggestion.

Errors

  • 400 VALIDATION_ERROR — empty text, text over 10,000 chars, or an unknown direction.
See Errors for the full error contract.

Moderation tasks

All moderation operations

Moderation overview

What it is and when to use it