How reliable is the prediction?

It is a statistical estimate, not a fact about the person. Genderize infers from how a first name is distributed across its data, so the result is a likelihood, and it is not a basis for Lyro to state a customer's gender back to them.

What does the country code change?

It localises the estimate. The same first name can skew differently from one country to another, so supplying a country code narrows the statistical base the prediction is drawn from and usually beats a global average.

What does Lyro need in order to run a prediction?

A first name, and nothing else. The action is keyed on that single input, so a record that carries only an email address, a surname, or a company name has nothing for this integration to work from.

Can Lyro classify a whole list of names at once?

The action predicts from one first name per call, so a list means a series of calls rather than a single batch request. Inside a conversation that is rarely a constraint - Lyro predicts for the person it is actually talking to.

Genderize MCP integration

Estimates the gender most often associated with a first name, optionally scoped to a country code, from the name a workflow already holds.

Connect Genderize See all integrations

1actions available

What your agent can do with Genderize

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

Predict gender
Lyro infers customer gender from first names to personalize interactions. Your team sends more relevant greetings and recommendations based on inferred customer attributes.

See all 1 actions

How businesses use Genderize + Lyro

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

Estimate the salutation from a first name
Lyro runs the Genderize prediction on the name a conversation already holds, so a greeting can be chosen without asking the customer to state it.
Predict GenderRead Prediction Confidence
Narrow the estimate to a country
The action takes an optional country code, so Lyro can ask for the estimate that fits the market a name comes from rather than a global average.
Predict GenderScope By Country Code
Segment a record from the name on it
For a workflow that needs a best guess for grouping, Lyro takes the estimate from the existing first name instead of adding a question to a form.
Predict GenderRead Prediction Confidence
Know when the guess is too weak to use
The prediction comes back with its confidence, so Lyro can say the name is inconclusive rather than committing to a wrong salutation.
Predict GenderRead Prediction Confidence

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 Genderize actions it has and picks the ones a request needs.

01
Connect Genderize
Authorize the Genderize 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 Genderize 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

Genderize · Lyro

Everything else about Genderize

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

It is a statistical estimate, not a fact about the person. Genderize infers from how a first name is distributed across its data, so the result is a likelihood, and it is not a basis for Lyro to state a customer's gender back to them.