Forum moderation that scales past your mod team
Every growing community hits the same wall: the mod queue grows faster than the mod team. ModerateHQ evaluates each post and comment as it arrives. Clear cases are approved or blocked automatically, and only genuinely borderline content lands in front of a human.
500 free requests every month · No card to start
The mod queue does not scale on goodwill
Mod burnout is real
Volunteers and small teams cannot read everything. Automatic verdicts on the clear cases mean humans only see the posts that need judgement.
Debate is not abuse
Heated disagreement, profanity, and blunt criticism are normal forum life. The community policy tolerates rudeness that stops short of targeted abuse, so your most engaged members are not the ones getting banned.
Spam arrives faster than reports
Crypto spam, phishing links, and scam posts get blocked on arrival instead of after your users have already seen and reported them.
What a verdict looks like
The community policy is calibrated for general communities: rude is allowed, targeted is not.
“This is honestly one of the worst takes I have read on this forum. Did you even read the article before posting?”
Direct but non-abusive disagreement: it criticises the argument without personal attack, slurs, or harassment.
A generic insult with no protected-class element and no pattern of targeting is allowed under the community policy.
“Keep replying and I will post your home address and workplace for everyone here to see.”
A direct threat to publish someone's private identifying information as punishment for their speech: doxxing and an intimidation threat at once.
The whole integration
Send a POST with your API key, the content, and optional context. You get structured JSON back with the verdict, categories, and a reason. That is the entire integration.
$ curl https://api.moderatehq.com/v1/moderate/text \
-H "x-api-key: $MODERATEHQ_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "This is honestly one of the worst takes I have read on this forum.",
"policy": "community",
"context": {
"platform": "my-forum",
"channelType": "discussion thread"
}
}'What the community policy covers
Balanced moderation for general online communities, forums, and social platforms. Remove clearly harmful content; tolerate rudeness, profanity, and heated disagreement that stops short of targeted abuse. A generic insult with no protected-class element and no pattern of targeting is allowed.
The full catalog, including the platform safety floor enforced on every request, is on the policies page and available programmatically without a key.
Frequently asked questions
Can I use this with Discourse, phpBB, or a custom forum?
Yes. It is a plain HTTP API, so anything that can make a POST request can use it: a Discourse plugin, a phpBB hook, or middleware in your own stack. You get JSON back and decide what approve, flag, and block mean in your software.
What happens to flagged posts?
That is your call. Most forums leave flagged posts up and route them to a review queue; stricter ones hold them until a moderator approves. The verdict is the source of truth and you wire it to whatever workflow fits your community.
Will it punish my regulars for swearing?
No. The community policy tolerates profanity, rudeness, and heated disagreement by design. If a corner of your product needs a tighter or looser line, use a different policy there: the policy is chosen per request, so a kids' space can run strict while the main forum runs community.
Can I run my existing backlog through it?
Yes. It is one request per piece of content, so you can replay history through the API at your own pace. One credit each, the same as live traffic.
Give your mod team their evenings back
Create an account, grab your API key, and send your first post with the community policy. The free tier needs no card.
Get started free