Kanji, kana and readings

The same characters can carry different signals

Kanji may have several readings, while a name can be written in hiragana, katakana or multiple romanized forms. Spelling and context therefore affect the available evidence.

askToAI=true extends coverage when database evidence is absent, but it does not make an ambiguous name certain. Allow unknown results and avoid high-impact decisions.

How can gender be inferred from a Japanese name?

GenderAPI evaluates the submitted name using Japanese name evidence and regional context, then returns a name-based prediction and probability when enough evidence is available.

Can I enter names in kanji, hiragana or katakana?

Yes. The tool accepts Unicode input in kanji and kana. Results depend on the spelling, reading ambiguity and available name evidence.

Do I need to separate the given name and family name?

No. You can submit the full Japanese name in one field. The response shows the name signal used for prediction.

Can I submit a romanized Japanese name?

Yes. A Latin-script romanization can be submitted, though alternative romanizations may produce different evidence and probability values.

How is AI used in this demo?

The demo sends askToAI=true with JP country context. AI fallback is considered when the database has no result; it does not guarantee an answer.

Are submitted name 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; see the Privacy Policy for details.

Build the integration

Use Japanese name context in your application

Review authentication, country context, AI fallback and response fields before implementation.

Continue testing

Use your GenderAPI key

Paste the API key from your GenderAPI account to continue testing after the public daily limit.

Stored only for this browser tab. It is cleared when the tab is closed.