Gender API determines the gender of a first name, email address, or username.
Gender API determines the gender of a first name, email address, or username. On Nagent, Gender API is exposed as a fully-configurable developer tools integration that any agent can call — 9 actions, and API key authentication. No code is required to wire Gender API into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Gender API to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Gender API into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Gender API, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GENDER_API_GET_COUNTRY_OF_ORIGINTool to retrieve a name's likely countries of origin. Use after confirming the name identifier.
Input parameters
Client-defined request ID for correlation (max 50 chars).
Email address to query; can be provided instead of first_name.
Full name to query; can be provided instead of first_name.
First name to query. Required if full_name and email are not provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_GET_COUNTRY_OF_ORIGIN_V1Tool to get the country of origin for a given first name using v1 API. Returns the most likely country where the name is most common.
Input parameters
First name to query country of origin for. Must contain at least one non-space character.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_GET_STATISTICTool to retrieve account statistics from Gender-API, including remaining credits and usage details. Use when you need to check your credit balance before performing further gender lookups.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_BY_EMAIL_ADDRESSDetermine likely gender from an email address by extracting and analyzing the name portion. Returns male/female/unknown with a confidence score. Optionally filter by country for improved accuracy. Check result_found to know if a determination was made; probability indicates confidence level.
Input parameters
Client-provided correlation ID
Valid IPv4 or IPv6 address
Email address to query for gender determination
Browser locale code (e.g., 'en_US')
ISO 3166 ALPHA-2 country code
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_BY_EMAIL_ADDRESS_MULTIPLEDetermine likely gender for multiple email addresses in a single batch request. Returns male/female/unknown with confidence scores for each email. Use for efficient bulk processing. Each result includes result_found flag and optional probability score.
Input parameters
List of email queries to process in a single batch request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_BY_FIRST_NAMETool to determine the gender of a first name. Use when you need to identify gender based on a given name.
Input parameters
Client-defined correlation ID, max 50 characters.
Valid IPv4 or IPv6 address.
Browser locale, e.g., 'en-US'.
ISO 3166 ALPHA-2 country code.
Name to query.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_BY_FULL_NAMETool to determine gender by splitting a full name. Use when you have an exact full name string and want to infer gender. Slightly less reliable for rare or ambiguous names.
Input parameters
Arbitrary ID (max 50 chars) for correlating batch responses.
Valid IPv4 or IPv6 address for geo-based gender inference.
Browser locale string (e.g., en_US) for more accurate inference.
ISO 3166 alpha-2 country code to hint regional gender conventions.
Full name to query; must contain at least one non-space character.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_GENDER_BY_FIRST_NAME_MULTIPLETool to determine gender for multiple first names in a single batch request. Use when you need to query gender for several names efficiently to save API credits and reduce latency.
Input parameters
List of name queries to process in a single batch request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GENDER_API_QUERY_GENDER_BY_FULL_NAME_MULTIPLETool to batch query gender for multiple full names in a single request. Use when you need to determine gender for multiple names efficiently. Each name can optionally include country, locale, or IP for more accurate regional inference.
Input parameters
List of name query items to process in a single batch request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 48 agents privately built on Nagent that already use Gender API.
Build on Nagent
Connect Gender API to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Gender API, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Gender API is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Gender API is connected, you configure its 9 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Gender API steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Gender API event fires, the agent kicks off automatically.
Every Gender API action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Gender API ships with 9 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Gender API together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Gender API-based workflows tailored to your business.