Screen user content before it goes live.

Pass every submission through profanity, sentiment, and spam checks to decide — automatically — what publishes, what's held for review, and what's dropped.

3-step workflow
11 crTotal cost per run, across 3 APIs
  • Profanity Filter1 cr
  • Sentiment Analysis5 cr
  • Spam Detector5 cr
The problem

User-generated content is a moderation firehose. Reviewing everything by hand doesn't scale; publishing everything is a brand risk. A lightweight gate handles the obvious cases so humans only see the gray area.

What you get

A publish / hold / reject decision for every submission, so moderators spend their time only on genuinely borderline content.

The workflow

How the calls chain together

Every response below is a live sample from the actual API — nothing mocked.

01
Profanity FilterPOST /v1/profanityfilter1 cr

Filter profanity

Detect and mask profane language, and get a cleaned version of the text back.

isProfanetruefilteredTextToday is so **** hot! Why the **** woul…
Sample response
{
  "isProfane": true,
  "filteredText": "Today is so **** hot! Why the **** would anyone go outside?",
  "mask": "*",
  "trimmed": false,
  "profaneWords": 2
}
passes a cleanliness flag to the next step
02
Sentiment AnalysisPOST /v1/sentimentanalysis5 cr

Read the tone

Score sentiment to route hostile or highly negative content toward review.

sentiment3isNegativefalse
Sample response
{
  "comparative": 0.25,
  "sentimentText": "positive",
  "sentiment": 3,
  "isPositive": true,
  "isNegative": false,
  "normalizedScore": 0.3
}
passes a tone signal to the next step
03
Spam DetectorPOST /v1/spamdetector5 cr

Catch spam

Flag likely spam, including disposable emails and blacklisted IPs in the submission.

likelySpamtrueisIPBlacklistedfalse
Sample response
{
  "likelySpam": true,
  "isDisposableEmail": false,
  "isIPBlacklisted": false,
  "ipDetails": {
    "country": "IN",
    "region": "DL"
  },
  "parsed": true
}

Recipe questions.

What to know before you wire it up.

Talk to the team
Can I auto-publish clean content?
Yes. When profanity is absent, sentiment is acceptable, and spam signals are clear, auto-publish; otherwise route to a review queue. You set the thresholds.
Does it handle languages other than English?
Profanity and sentiment work best on the languages they support; pair with the language-detector API first if you accept multilingual input and want to branch accordingly.
What about image content?
This recipe covers text. For images, add an image-moderation or OCR step to extract and screen embedded text before publishing.

Cook this in an afternoon. Every API in this recipe shares one key, one response shape, and one bill.

Swap in your own APIs

Every step is a catalog API — mix and match freely.

Browse the catalog