Gender Detector API

About the Gender Detector API

Gender Detector works by analyzing the name provided and predicting the likely gender of the person. It uses a machine learning model trained on a large dataset of names and their associated genders to make the prediction.

What people use it for

Email Salutation Selection

When drafting automated outreach, sales platforms choose correct honorifics and greeting styles based on the predicted gender returned for each recipient.

Account Profile Onboarding

Assign default avatars and profile pronouns automatically when a user signs up by matching their entered first name against regional gender predictions.

Audience Demographic Audits

To evaluate subscriber breakdowns without intrusive survey forms, newsletter editors tabulate aggregate gender distributions across their imported subscriber lists.

Personalized Catalog Navigation

Ecommerce fashion apps preselect relevant apparel landing tabs for new accounts by checking customer first names against country-specific gender results.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/genderdetector

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Optional

1
2

curl "https://api.apiverve.com/v1/genderdetector?name=John%20Mcdonald&country=US" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/genderdetector

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10

{
  "status": "ok",
  "error": null,
  "data": {
    "name": "John Mcdonald",
    "country": "US",
    "detected": true,
    "gender": "male"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Gender Detector form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Gender Detector API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1