Genderize.io API

Beginner's Pick Development / No Auth Required Beginner HTTPS CORS
Free to Use 25 per window
78 B
Measured Score 0 50 100 Speed 10/30 Consistency 20/20 Security 18/20 Browser access 15/15 Transparency 15/15 TESTED 2026-08-10

Overview

Genderize.io predicts the likely gender of a given first name using a statistical model trained on a database of over 100 million names from around the world. It returns the predicted gender along with a probability score and the count of name samples used — giving you a confidence measure for each prediction. The API is free for up to 1,000 names per day without authentication.

Beginner Tip

This is one of the simplest APIs you can call — just pass a name in the URL query string and get back a JSON object. No API key required for the free tier. You can also pass a country_id parameter (ISO 3166-1 alpha-2) to get region-specific predictions, since the same name can lean differently by country.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://api.genderize.io?name=alice
Result
HTTP 200 · application/json · 68 bytes · compressed
Response time
323 ms (median of 3) · fastest 313 ms
Transport
TLSv1.2 · ECDHE-RSA-AES128-GCM-SHA256 · certificate issued by Let's Encrypt
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Rate limit
25 per window
Served by
nginx/1.16.1
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
count integer 399418
name string alice
gender string female
probability number 0.99

Captured Response

Captured from a real request to https://api.genderize.io?name=alice on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "count": 399418,
  "name": "alice",
  "gender": "female",
  "probability": 0.99
}

Field Reference

name The input first name as provided in the query, returned as-is.
gender Predicted gender: "male", "female", or null if the name is not in the database.
probability Confidence score from 0.0 to 1.0 — higher means stronger evidence for the predicted gender.
count Number of data samples for this name in the Genderize.io database — larger counts mean more reliable predictions.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://api.genderize.io?name=alice";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 404 Requesting a path that does not exist text/html

Returned an HTML error page rather than JSON — worth knowing if your client assumes every response can be parsed as JSON.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

probability: 0 or null result The name is not in the Genderize.io database, often due to unusual spelling or a very rare name
Try common alternate spellings or handle the null case gracefully in your code as a name-not-found state.
429 Too Many Requests The free tier limit of 1,000 requests per day has been exceeded
Batch multiple names in a single request using repeated name[] parameters (e.g., ?name[]=alice&name[]=bob) to stay within limits, or subscribe to a paid plan.
Inaccurate prediction for unisex names Names like Alex or Jordan have roughly 50/50 distribution, leading to low probability scores
Check the probability field — if it is below 0.7, treat the prediction as uncertain and avoid acting on it without additional signals.

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 10/30
Consistency 20/20
Security 18/20
Browser access 15/15
Transparency 15/15
Endpoint Response Time 323ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS YES
Category Development
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →