What a Content Moderation API Actually Returns

Adding a content moderation API to an existing product is a one-afternoon job if you know two things before you write any code: exactly what the endpoint returns, and who owns the policy decision. With CautionLabs, the endpoint returns flags. Your application decides what those flags mean.

That split is the whole design. A moderation model that hands you a float forces you to invent a cutoff, defend it in code review, and revisit it whenever the model changes. A model that hands you booleans moves the policy conversation out of the model and into your application, where your product context actually lives.

Booleans, not confidence scores

Every successful response from the CautionLabs cloud API contains thirteen booleans: twelve per-category flags and one overall result.

Twelve keys inside a categories object, each true or false .

One top-level flagged boolean that is true when any category is flagged.

There are no scores, no probabilities, and no…