Check usernames for profanity, slurs, hate speech, and inappropriate content. Catches leetspeak variations, character substitutions, and hidden offensive words. Perfect for user registration flows.
{
"status": "ok",
"error": null,
"data": {
"username": "b00bs",
"isProfane": true
}
}






Check usernames for profanity, slurs, hate speech, and inappropriate content. Catches leetspeak variations, character substitutions, and hidden offensive words. Perfect for user registration flows.
A single authenticated GET with the location you care about — no SDK required.
GET /v1/usernameprofanity?query=… x-api-key: your_key
Each request pulls from multiple upstream sources and computes the derived fields for you.
One structured object, typically under 200 ms — ready to render.
{ username, isProfane, … }
Real applications shipping on this endpoint today — each with the numbers that made it worth wiring up.
See every use caseIntegrate username profanity checking into your registration flow. Block inappropriate usernames in real-time before accounts are created, protecting your community.
Add profanity checking to your username validation pipeline. Combine with username availability checks to provide instant feedback during signup.
Copy a working request, or install a typed SDK. Same endpoint, same key.
const res = await fetch("https://api.apiverve.com/v1/usernameprofanity?username=b00bs", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Every related API ships with your key — no separate plans, no extra keys, one bill.
See pricingReady-made recipes for Zapier, Make, and n8n — trigger on an event, and the data lands where your team works.
The same key unlocks every other APIVerve endpoint — reach for them when you need them.
Browse the catalog