gender-api

name

gender-api

description

Gender-API is a data enrichment API that predicts gender from first names, email addresses, or social profiles, enabling developers and data teams to enrich customer records, personalize workflows, and support segmentation or analytics use cases in applications and pipelines. Read and write Gender-API data through One: gender, genderbyemailaddress, genderbyemailaddressmultiple, countryoforigin, accountstatistics, signup and more, 9 actions with real parameter documentation. Use whenever the user asks to look something up in Gender-API, create or update a record there, or build code against the Gender-API API.

Gender-API through One

Gender-API is a data enrichment API that predicts gender from first names, email addresses, or social profiles, enabling developers and data teams to enrich customer records, personalize workflows, and support segmentation or analytics use cases in applications and pipelines.

One exposes Gender-API through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform gender-api if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Gender-API is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.