NameAPI is a web API
to handle people's names
in your software.

News

30.10.2025

Software Version 11.0.0 Deployed

Release of Optimaize PII Platform with Java 21.


29.09.2025

Dictionary Update: Quechua and Aymara Names

The NameAPI database continues to grow, now enriched with 3,700 new given names and 600 family...


29.08.2025

Database Expansion: Brazilian Portuguese Names

We’ve expanded our database to include a comprehensive set of Brazilian Portuguese names. This...


21.08.2025

Secondary Domain Added: api.name-api.com for Enhanced Redundancy

To further strengthen NameAPI’s reliability and provide uninterrupted service access, we are happy...


28.07.2025

Version 10.8.0 Released

Release of Optimaize PII Platform, version 10.8.0.


   

Generic Person Genderizer

       
Attempts to detect the person's gender based on the inputs, especially the person's name.
                    

   

Input

       
See person.
       
See context.
       
(todo: add example)

   

Output

       
Possible values:

The person is clearly 'male'.

The person is clearly 'female'.

Can be either male or female. See malePercent.

No gender could be computed, but better intelligence should be able to tell the gender. An example is a name input of which we have never heard before.

From the given data it is or seems impossible to tell the gender.
For example all terms are gender-inapplicable, or there are no names at all. Thus this differs from NEUTRAL where something is clearly known to be neutral.

There are conflicting genders in the given data.
Example: "Mr Daniela Miller" (salutation vs. given name).
The input data must be manually reviewed. It is impossible and useless to make a guess (garbage in would only cause garbage out).

       
If neutral (otherwise null) then this may be specified (but does not have to be), 0-100, the remaining % are for female.
       
0-100 where 100 is the best.
       
(todo: add example)