Genderize Name Gender Scraper
Pricing
from $4.52 / 1,000 results
Genderize Name Gender Scraper
Predict gender from a list of first names using the Genderize.io API. Each result returns the name, predicted gender, and probability. Supports country localization and batch processing up to a million names.
Pricing
from $4.52 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
14 days ago
Last modified
Categories
Share
Genderize Name Gender Scraper
Predict gender from any list of first names using the public Genderize.io API, up to a million names per run. Each result returns the predicted gender, probability, and count, with an optional country filter. No API key required. Export to JSON, CSV, Excel, or XML.
Manually guessing the gender of thousands of first names for a CRM cleanup or research dataset is slow and inconsistent. This Actor sends each name to the Genderize.io public API and returns a structured prediction. You get a clean dataset with the name, its most likely gender, and a confidence probability, ready for analysis or database enrichment.
| Who uses it | What they scrape Genderize.io for |
|---|---|
| CRM administrators | Enrich contact records with a probable gender for personalization and segmentation. |
| Market researchers | Analyze the gender distribution of a sample of first names from a survey or user list. |
| Data analysts | Clean and standardize a list of first names by appending a gender probability score. |
| HR tech developers | Pre-process applicant name lists for anonymized demographic reporting. |
What it does
This Actor collects gender predictions for a list of first names from the Genderize.io API and returns each name as a flat row with its predicted gender and probability.
- 🌍 Global or local prediction: Leave the country code empty for a worldwide prediction, or add an ISO 3166-1 alpha-2 code to localize the gender guess.
- 📊 Probability score: Every prediction includes a probability between 0 and 1, so you can filter out low-confidence results.
- 📋 Batch processing: Paste in a list of names and the Actor processes them sequentially, respecting API rate limits automatically.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Genderize.io data
🧹 Clean a CRM contact list.
A marketing ops manager pastes 50,000 first names with a US country code to append a gender field for email campaign segmentation.
📊 Profile survey respondents.
A researcher runs a list of respondent first names through the Actor to estimate the gender split of a study sample.
🔍 Validate user-submitted data.
A data engineer compares the predicted gender against a user's self-reported gender to flag potential data entry errors.
🌐 Localize a global name list.
An analyst runs the same name list with different country codes to see how gender predictions shift across regions.
Why choose this scraper
| What you get | |
|---|---|
| No API key | Uses the public Genderize.io endpoint with no registration or token required. |
| Structured output | Every name becomes one flat row with name, gender, probability, and count. |
| Country filter | Narrow the prediction to a specific country's naming patterns for higher accuracy. |
| Scale ready | Process up to a million names per run, ideal for large CRM backfills. |
How it compares
This Actor focuses exclusively on the Genderize.io API for gender prediction, while other name scrapers bundle age and nationality APIs into a single run.
| Feature | ParseForge | Genderize Name Scraper | Name Analysis Scraper - Gender, Age & Nationality | Name Insights - Age, Gender, Nationality from First Name |
|---|---|---|---|---|
| Gender prediction from Genderize.io | Yes | Yes | Yes | Yes |
| Age prediction from Agify.io | Not listed | Not listed | Yes | Yes |
| Nationality prediction from Nationalize.io | Not listed | Not listed | Yes | Yes |
| Country filter for localized gender | Yes | Not listed | Not listed | Not listed |
| No API key required | Yes | Yes | Yes | Yes |
| Batch size up to 1,000,000 names | Yes | Not listed | Not listed | Not listed |
Configure the run
Drive the Actor from a list of first names and an optional two-letter country code. The country filter localizes the prediction before the result is written to your dataset. The Input tab lists every parameter.
A first run with the defaults:
{"names": ["Peter","Maria","Alex","Kim","Sofia"],"maxItems": 10}
A larger pull:
{"names": ["Peter","Maria","Alex","Kim","Sofia"],"maxItems": 200}
Pricing
Pay-per-result: $0.005 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.50 |
| 1,000 results | $5.00 |
| 10,000 results | $50.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Genderize Name Gender Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Genderize.io through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/genderize-names-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting null gender for many names?
The Genderize.io database may not have enough data for those names. Try adding a country code to narrow the search, or check for typos and extra spaces in your name list.
The run stopped before processing all my names.
The free Genderize.io API allows 1000 names per day per IP address. If you exceed that, the API returns a 429 error. Wait 24 hours or use a paid API key with a higher limit.
I get a 429 Too Many Requests error.
You have hit the daily rate limit. The Actor includes automatic retries, but if the limit is exhausted, you must wait until the limit resets or subscribe to a paid Genderize.io plan.
The gender prediction seems wrong for a specific name.
Genderize.io predictions are based on public data and may not reflect an individual's actual gender. Use the probability score to filter for high-confidence predictions only, and always treat the output as a statistical guess.
My CSV export has empty gender columns.
Empty fields mean the API returned a null value for that name. This is expected for rare or unisex names. You can filter these rows out in your spreadsheet software.
FAQ
| Question | Answer |
|---|---|
| Do I need a Genderize.io API key? | No. This Actor uses the free public API endpoint, which allows up to 1000 names per day from a single IP address without a key. |
| What does the probability score mean? | It is the API's confidence that the predicted gender is correct, ranging from 0 to 1. A score of 0.99 means the model is 99% sure based on its training data. |
| Can I filter predictions by country? | Yes. Provide a two-letter ISO 3166-1 alpha-2 country code like US, DE, or FR in the input, and the API will localize the prediction to that country's naming data. |
| How many names can I process in one run? | You can set the maximum names field up to 1,000,000. The free API has a daily rate limit of 1000 names per IP, so larger runs may need to be spread across multiple days or use a paid API key. |
| What happens if a name is not found? | The API returns a null gender and a null probability. The Actor still writes a row for that name so you can see which names could not be predicted. |
| Can I use this for non-English names? | Yes. The Genderize.io database includes names from many cultures. Using the country filter improves accuracy for names that are common in specific regions. |
| Is the data exportable? | Yes. You can download your results in JSON, CSV, Excel, or XML format from the Apify dataset tab. |
| Does this Actor predict age or nationality too? | No. This Actor only calls the Genderize.io API for gender prediction. For age or nationality, you would need a different Actor that integrates with Agify.io or Nationalize.io. |
| How do I format the name list? | Enter one first name per line in the input field. The Actor trims whitespace and sends each name as a separate API request. |
| Can I run this on a schedule? | Yes. You can set up an Apify schedule to re-process a static name list or trigger the Actor via API with a dynamic list. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Genderize.io. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
