Questions about the Username Profanity API

The things developers ask before wiring up the Username Profanity API — what it returns, what it covers, and where the limits are. Straight answers, no fluff.

Everything you asked

Still stuck on something specific? The team answers real integration questions directly.

Contact support
Does it catch leetspeak and character substitutions?
Yes! Our API detects common evasion tactics like leetspeak (e.g., "4ss" instead of "ass"), character substitutions (using 0 for o, 1 for i), and intentional misspellings designed to bypass filters.
What languages are supported?
We support profanity detection in English, Spanish, French, German, and other major languages. The API automatically handles multilingual usernames.
How do I handle borderline cases?
The API returns a binary isProfane flag. For additional context, you can combine this with our Profanity Filter API which provides word counts and filtered text.
Does it detect hidden words within usernames?
Yes! The API identifies offensive words embedded within longer strings, such as profanity hidden in the middle of otherwise innocent-looking usernames.
Can I customize the word list?
Our API uses a comprehensive, regularly-updated profanity database. For custom blocklists, you can combine our API with your own additional checks.
Is it suitable for children's platforms?
Absolutely. The API catches leetspeak and hidden profanity that basic filters miss. Many gaming and education platforms rely on our API for children's safety.

Answer the last question by building. Free tier, no card — run the Username Profanity API in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales