Review social datasets
Add a likely name and prediction field where records contain only handles.
Live username gender lookup
Determine gender from a username
Find a likely personal name inside a social handle, nickname or display name and return a name-based gender prediction when enough evidence is available.
- Name signal extraction
- AI fallback enabled
- Live JSON response
A username may represent a brand, character or idea rather than a person. Treat the result as an inferred signal—not self-identified gender.
Try it online
Analyze a username
Enter a handle with or without the @ symbol. AI fallback is enabled when the extracted name has no database result.
Example response shown below. Select Analyze username to run a live lookup.
Example JSON response
{
"status": true,
"q": "emilyblack",
"name": "emily",
"gender": "female",
"country": "US",
"probability": 100
}How it works
From social handle to a reviewable signal
GenderAPI cleans the handle, looks for a likely personal name and evaluates that name against its available evidence.
- 01Submit the handle
Send a username, nickname or display name. The leading @ symbol is optional in this demo.
- 02Extract a likely name
Separators, numbers and surrounding handle text are evaluated to isolate the useful name signal.
- 03Review the prediction
Check the extracted name, gender and probability. Accept that weak aliases may remain unknown.
Where it can help
Enrich username-based datasets carefully
Use the extracted signal as one optional field in an auditable workflow.
Complete partial profiles
Support record enrichment while preserving unknown and low-confidence outcomes.
Work with aggregate patterns
Evaluate groups and trends without treating an inferred attribute as an individual fact.
AI and limitations
AI fallback improves coverage—not certainty
askToAI=true lets the endpoint consult AI only when the extracted name has no database result. It does not force an answer for every alias.
Handles such as @emily.jane provide clearer name evidence than @cool_x99. Keep an unknown state, inspect probability and avoid high-impact decisions.
Frequently asked questions
Gender from username FAQ
Can GenderAPI determine gender from a social media username?
When a username contains a recognizable personal name, GenderAPI can extract that signal and return a name-based gender prediction. Abstract aliases may return no result.
Why does GenderAPI extract a name first?
The prediction is based on name evidence. Extracting a likely name separates that evidence from numbers, separators and other characters in the handle.
Which usernames provide the clearest signal?
Handles such as emily.jane or robert89 contain recognizable name elements. Brand names, role accounts and fantasy aliases provide weaker or no personal-name evidence.
How does AI fallback work in this demo?
The demo sends askToAI=true. AI fallback is considered only when the extracted name has no database result; it does not guarantee a prediction.
Are username queries stored?
The published policy says successful inputs are not retained as reusable query records. Technical and security logs follow a separate retention schedule. A query for which no gender can be found may be retained to improve GenderAPI; review the Privacy Policy for details.
Build the integration
Connect username analysis to your application
Review authentication, AI options, request parameters and response fields before implementation.