How does Lyro tell a confident gender match from a guess?

Every lookup returns a result_found flag and a probability score alongside male, female, or unknown. Lyro reads both, so a low-probability result can be treated as unknown rather than acted on, and rare or ambiguous full names get flagged instead of resolved wrongly.

Whose Gender-API credits does a lookup spend?

The credits on the Gender-API account you connect. Get Gender API Statistics returns the remaining balance and usage detail, which is also why the batch actions exist: Query Gender by Multiple First Names resolves a list in one request instead of one charged call per name.

Can Lyro write the enriched gender back into our CRM record?

Not through this toolkit. Every Gender-API action here is a read - name, email, and country lookups plus account statistics - so nothing in it writes to a profile. The enriched value has to be persisted by whichever CRM or database toolkit you connect alongside it.

Does accuracy improve for names outside the English-speaking world?

Yes, when you pass the region. The email and batch full-name actions accept an optional country, locale, or IP hint that narrows the inference, and Get Country of Origin tells you which regions a name actually belongs to before you pick one.

Gender api MCP integration

Resolves a name or email to a likely gender with a confidence score, batches whole lists in one call, and reports the credits each lookup leaves.

Connect Gender api See all integrations

9actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Gender from first name
Lyro predicts the likely gender of a first name. Personalizes outreach with correct pronouns and naming conventions.
Query gender by email address
Lyro infers gender from an email address by analyzing the name portion. Enriches contacts without asking them directly.
Query gender by full name
Lyro splits a full name and predicts gender. Bulk-enriches entire contact lists programmatically in seconds.

See all 9 actions

How businesses use Gender api + Lyro

Each card is one request a support team gets, and the Gender api actions Lyro runs to close it.

Resolve a first or full name to a likely gender
Lyro passes the name it already has in the conversation and gets male, female, or unknown back with a probability score, so a reply is personalised only when the confidence is actually there.
Gender From First NameQuery Gender By Full Name
Work from an email address when there is no name field
Where a record holds only an address, Gender-API extracts and analyses the name portion, and Lyro can push a set of addresses through in one request rather than one lookup at a time.
Query Gender By Email AddressQuery Gender By Multiple Emails
Check which countries a name is most common in
Lyro returns the likely countries of origin behind a name, which is what tells a team whether an ambiguous result is genuinely ambiguous or just unusual in the locale they assumed.
Get Country Of OriginGet Country Of Origin (V1)
Batch a whole list and watch the credit burn
Lyro sends many first names or full names in a single request, each optionally carrying a country or locale hint, then reads the account statistics so nobody finds the credit balance empty halfway through.
Query Gender By Multiple First NamesQuery Gender By Full Name (Multiple)Get Gender API Statistics

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Gender api actions it has and picks the ones a request needs.

01
Connect Gender api
Authorize the Gender api account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Gender api actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Gender api · Lyro

Everything else about Gender api

Setup, permissions, and the limits of what Lyro can do inside Gender api.

Every lookup returns a result_found flag and a probability score alongside male, female, or unknown. Lyro reads both, so a low-probability result can be treated as unknown rather than acted on, and rare or ambiguous full names get flagged instead of resolved wrongly.

Every action available in Gender api

All 9 actions your agent can call on Gender api, straight from the live MCP connection.

Get country of origin
Retrieve a name's likely countries of origin.
Get country of origin (v1)
Get the country of origin for a given first name using v1 API.
Get gender API statistics
Retrieve account statistics from Gender-API, including remaining credits and usage details.
Query gender by email address
Determine likely gender from an email address by extracting and analyzing the name portion.
Query gender by multiple email addresses
Determine likely gender for multiple email addresses in a single batch request.
Gender from first name
Determine the gender of a first name.
Query gender by full name
Determine gender by splitting a full name.
Query gender by multiple first names
Determine gender for multiple first names in a single batch request.
Query gender by full name (multiple)
Batch query gender for multiple full names in a single request.