Respect right-to-left names
Keep the original value in your dataset and add prediction fields separately.
Arabic name gender lookup
Analyze a single or full name written in Arabic script and return a name-based gender prediction with regional context and probability when available.
Arabic naming practices vary across regions, languages and communities. Treat the result as an inferred signal—not self-identified gender.
Try it online
Submit a single or full name. This demonstration adds SA context and AI fallback automatically.
Example response shown below. Select Analyze name to run a live lookup.
{
"status": true,
"q": "ليلى الخطيب",
"name": "ليلى",
"gender": "female",
"country": "SA",
"probability": 94
}How it works
The API accepts a complete Unicode name and evaluates it with the country context supplied by the request.
Use a given name or full name in natural right-to-left Arabic script, with or without diacritics.
This demo uses SA. A production request should use the known country code for the record.
Check the extracted name, gender and probability; keep ambiguous outcomes unknown.
Arabic-script data
Original-script input preserves characters and diacritics that may be lost or changed during Latin transliteration.
Keep the original value in your dataset and add prediction fields separately.
Submit the full name without assuming one universal Arabic name structure.
Account for differences across the Gulf, Levant, North Africa and diaspora communities.
Region and transliteration
Religious, family, tribal and regional conventions vary. The same name may also have several Latin transliterations, so original Arabic spelling and country context can be useful.
askToAI=true extends coverage when database evidence is absent, but does not make an ambiguous name certain. Allow unknown results and avoid high-impact decisions.
Frequently asked questions
GenderAPI evaluates the submitted name using Arabic name evidence and the supplied regional context, then returns a name-based prediction and probability when enough evidence is available.
Yes. The API accepts either format in one field. You do not need to split the name before using this demo.
The input accepts Unicode Arabic script, including names with diacritics. Spelling and regional variation can affect the available evidence.
No. SA is the regional context used by this demonstration. Production integrations should send the applicable country code when it is known.
The demo sends askToAI=true with SA country context. AI fallback is considered when the database has no result; it does not guarantee an answer.
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; see the Privacy Policy for details.
Build the integration
Review authentication, country context, AI fallback and response fields before implementation.