Gender-API.com alternatives: price, limits and what we have not measured

Gender-API.com is one of the oldest name-to-gender services, running since 2014, and it has the widest set of native integrations in this market. Teams usually look for an alternative for one of three reasons: the price at volume, the 100-lookup free tier, or a ceiling of one million lookups a month on its public plans.

This page was checked against Gender-API.com's own pricing page, documentation and home page on October 14, 2026. We run NameGender, one of the alternatives below, so read the numbers rather than our conclusions. One thing up front: we have not measured Gender-API.com's accuracy. Our benchmark covers Genderize and Namsor; for Gender-API.com, the section on testing below is the honest answer.

What Gender-API.com does well

• Native integrations. HubSpot, Salesforce, Mailchimp, Klaviyo, Shopify, Stripe and an Excel add-in, plus a Google Sheets add-on. If your workflow lives in one of those tools and you do not want an automation step in between, nobody else in this market covers as many.
• Inputs beyond a first name. First names, full names split into first and last name, and email addresses, with a country hint and batches of 100.
• Nationality. It also estimates the nationality behind a name, which a gender-only API does not.
• Account features. Up to 50 seats per account and two-factor login.

If those are the reasons you chose it, price alone may not justify the work of switching.

Price at the same volume

Monthly cost of the cheapest published plan that covers each volume, checked on October 14, 2026, in each vendor's own currency.

Three differences matter more than the totals:

• Above one million a month, Gender-API.com publishes no plan. NameGender sells 10 million for €333 one-off or €266.40 a month, and quotes above that.
• One-off purchases. Gender-API.com's one-off packs are valid for 12 months after the last purchase. NameGender's one-off credits stay on the balance until they are spent, which matters if you enrich a list once or twice a year.
• Free tier. Gender-API.com gives 100 free lookups a month. NameGender gives 500 at sign-up and 100 a day, enough to test on a real sample before paying.

What NameGender adds and what it lacks

What it adds:

• A ready salutation in ten languages (Mr/Ms, Herr/Frau, Monsieur/Madame, Sr./Sra. and others), so the step from gender to greeting is not yours to build.
• The evidence behind each answer: the number of records, the share, a confidence tier and the source. A result based on 50 records is marked differently from one based on four million.
• Unknown instead of a guess for company names, role inboxes such as info@ and sales@, and names without enough evidence.
• Usernames as an input, and surname-first full names ("Dupont Marie") read in the right order.

What it lacks, compared with Gender-API.com: native HubSpot, Salesforce, Mailchimp and Klaviyo apps (NameGender reaches them through Zapier, Make or n8n), nationality estimates, team seats and two-factor login for password accounts. It is also a much younger service.

Testing a switch on your own list

Because we have not measured Gender-API.com, do not take a vendor table as the answer. The test takes an afternoon:

1. Export 500 to 1,000 names from your own data with the country, where you have it, and a column you can check the answer against, such as a title already in your CRM.
2. Run the same file through both services. NameGender's free credits cover it; Gender-API.com's free tier covers 100 names, so a small paid pack is needed there.
3. Count three things separately for each: how many names got an answer, how many of those answers were right, and how many were wrong with high confidence. The last one is what puts the wrong salutation in front of a customer.
4. Look at your largest country and your largest non-Latin script on their own. A global average can hide a weak market.

The method we use for our own benchmark describes the same steps in more detail.

Moving the integration

Gender-API.com returns gender, an accuracy from 0 to 100 and samples. NameGender returns gender, a probability from 0 to 100 and sample_size, so most integrations change a URL, the authentication header and two field names. The batch limit is the same 100 names per request. The API reference lists every field, and the client libraries cover ten languages.

Related: the measured comparison of four gender APIs, Genderize alternatives and Namsor alternatives.