What changes between these APIs?
GenderAPI.io and Gender-API.com are separate services. Both document name and email inference, but their request models, unknown values and charging rules differ. Similar product names and V2 labels do not make their endpoints or credentials interchangeable.
| Decision point | GenderAPI.io V2 | Gender-API.com | Sources |
|---|---|---|---|
| Name and email inputs | Names, email addresses and usernames use type and value on /api/v2/gender. A full-name input does not promise a complete first/last-name split. | V2 pages document first_name, full_name and email, including extracted first_name and last_name. | [1][13][11] |
| Request and authentication | Authorization: Bearer with a GenderAPI.io key. Query keys are available for simple GET examples; prefer headers in applications. | Bearer-authenticated JSON POST. Human reference and OpenAPI show different route forms; see the integration note below. | [2][12][14] |
| Country context | Optional country; inspect match.scope and match.country to see selected evidence. | Optional country, locale or ip in the reviewed first-name reference. | [3][12] |
| Confidence and unknowns | data.confidence is 0–1 or null. confidence_kind distinguishes stored-count frequency from an AI score; sample_count is null for AI. data.result_status: unknown; data.gender and data.confidence are JSON null. Inspect data.reason. | result_found, gender (including unknown), probability 0–1 and details.samples. Equal sample counts can produce unknown. | [3][12][14] |
| Batch requests | Up to 50 keyed items or 10 IP-trial items. Each item can have its own type, country and options. | Arrays are documented. Published batch limits differ between references; confirm the limit for your selected route. | [5][9][15] |
| AI and username controls | Explicit off, fallback or always. Singles default to fallback; batches default to off. Optional forceToGenderize uses the dataset first, then nickname-aware AI. | The reviewed V2 request tables do not document equivalent AI switches or a dedicated username field. | [4][14] |
| Unknown-result billing | Ordinary successful lookups cost 1 credit, even unknowns and fallback AI. Always-AI costs 2. forceToGenderize costs 1 for a resolved dataset result or 2 when AI runs. | The billing FAQ says only found results count, and each name is counted separately. | [6][10] |
Before you switch an integration
The human V2 reference shows /v2/gender, while the official OpenAPI uses routes such as /v2/gender/by-first-name and /by-email-address. The generic batch FAQ says 100 names; the Python client page says 1,000. We did not execute these routes to resolve the differences. Confirm the current contract for your chosen route before generating a client.
When moving to GenderAPI.io V2, replace first_name/full_name/email inputs with type and value. Replace checks for the string unknown with explicit data.result_status and null handling. Read meta.usage.charged_credits and billing_status; an unknown GenderAPI.io result can be billable. Reassess confidence thresholds instead of carrying them over automatically.
Evaluate the workflow you will deploy
Choose a representative sample you are permitted to process and keep the original inputs, preprocessing and country context fixed. Evaluate name, email and username workflows separately. Record provider, endpoint, date, configuration and whether AI was used.
Measure coverage (answered / eligible), accuracy among answered results (correct / answered), and correct results across all eligible inputs (correct / eligible). Report unknowns, errors, costs and latency separately. A threshold should be selected on validation data and then checked on a held-out sample.
GenderAPI.io does not publish an independent reference-labelled accuracy benchmark here. Database counts, contract tests and one provider's published study cannot establish which service will work best on your data. An inferred association does not establish a person's gender identity.
Sources:[7]
Frequently asked questions
Are GenderAPI.io and Gender-API.com the same API?
No. This page compares separate services. Check the domain in your base URL, documentation and account dashboard before copying a key or request.
Sources and review dates
Use the linked documentation to confirm current terms and behavior before choosing a provider.
- GenderAPI.io V2 request parametershttps://www.genderapi.io/docs/v2/request-parametersReviewed
- GenderAPI.io V2 authenticationhttps://www.genderapi.io/docs/v2/authenticationReviewed
- GenderAPI.io V2 responseshttps://www.genderapi.io/docs/v2/responsesReviewed
- GenderAPI.io V2 AI optionshttps://www.genderapi.io/docs/v2/ai-optionsReviewed
- GenderAPI.io V2 batch guidehttps://www.genderapi.io/docs/v2/batchReviewed
- GenderAPI.io V2 credits and usagehttps://www.genderapi.io/docs/v2/credits-and-usageReviewed
- GenderAPI.io accuracy methodologyhttps://www.genderapi.io/accuracy-methodologyReviewed
- GenderAPI.io pricinghttps://www.genderapi.io/priceReviewed
- Gender-API.com FAQ: Can I query multiple names in one request?https://gender-api.com/en/frequently-asked-questions/can-i-query-multiple-names-in-one-requestReviewed
- Gender-API.com FAQ: How do requests get counted?https://gender-api.com/en/frequently-asked-questions/how-do-requests-get-countedReviewed
- Gender-API.com v2: Query by email addresshttps://gender-api.com/en/api-docs/v2/query-by-email-addressReviewed
- Gender-API.com v2: Query by first namehttps://gender-api.com/en/api-docs/v2/query-by-first-nameReviewed
- Gender-API.com v2: Query by full namehttps://gender-api.com/en/api-docs/v2/query-by-full-nameReviewed
- Gender-API.com official OpenAPI descriptionhttps://gender-api.com/openapi/openapi.ymlReviewed
- Gender-API.com Python code exampleshttps://gender-api.com/en/code-examples/pythonReviewed