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



Slovene names: Unraveling a Fascinating Blend of Cultures

Did you know that Slovenian’s great variety of names reflects the country’s fascinating blend of...


Expanding Horizons: Introducing Fresh Additions to Our Name Database!

Collaborating diligently with natives worldwide, our research team has successfully integrated new...


Introducing the Latest Version: Java Client Library 6.0.0

The new and noteworthy feature of the Java™ Client Library 6.0.0 is its migration to Java 17.


Discover Our Name Parser Service

Efficiently and accurately analyze personal names, regardless of cultural or linguistic variations,...


Bulgarian Names: Stories of Tradition and Identity

Did you know that within the Bulgarian culture, name days often hold greater significance and are...


Generic Person Genderizer

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



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



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)