# GenderAPI.io vs Gender-API.com

> Compare GenderAPI.io V2 with Gender-API.com: separate accounts, name and email inputs, response fields, unknown billing, batch documentation and migration checks.

Canonical HTML: https://www.genderapi.io/genderapi-io-vs-gender-api-com

Last reviewed: 2026-09-26

## About this comparison

Published by GenderAPI.io, one of the providers discussed. This is a dated review of public documentation, not an independent performance test or an endorsement by another provider. We did not run competitor prediction requests. Undocumented in a reviewed reference does not mean unavailable. Recheck the linked contract and pricing before integrating.

## 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. | [GenderAPI.io V2 request parameters](https://www.genderapi.io/docs/v2/request-parameters); [Gender-API.com v2: Query by full name](https://gender-api.com/en/api-docs/v2/query-by-full-name); [Gender-API.com v2: Query by email address](https://gender-api.com/en/api-docs/v2/query-by-email-address) |
| 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. | [GenderAPI.io V2 authentication](https://www.genderapi.io/docs/v2/authentication); [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name); [Gender-API.com official OpenAPI description](https://gender-api.com/openapi/openapi.yml) |
| 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. | [GenderAPI.io V2 responses](https://www.genderapi.io/docs/v2/responses); [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name) |
| 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. | [GenderAPI.io V2 responses](https://www.genderapi.io/docs/v2/responses); [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name); [Gender-API.com official OpenAPI description](https://gender-api.com/openapi/openapi.yml) |
| 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. | [GenderAPI.io V2 batch guide](https://www.genderapi.io/docs/v2/batch); [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-request); [Gender-API.com Python code examples](https://gender-api.com/en/code-examples/python) |
| 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. | [GenderAPI.io V2 AI options](https://www.genderapi.io/docs/v2/ai-options); [Gender-API.com official OpenAPI description](https://gender-api.com/openapi/openapi.yml) |
| 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. | [GenderAPI.io V2 credits and usage](https://www.genderapi.io/docs/v2/credits-and-usage); [Gender-API.com FAQ: How do requests get counted?](https://gender-api.com/en/frequently-asked-questions/how-do-requests-get-counted) |

## 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.

Sources: [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name); [Gender-API.com official OpenAPI description](https://gender-api.com/openapi/openapi.yml); [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-request); [Gender-API.com Python code examples](https://gender-api.com/en/code-examples/python); [GenderAPI.io V2 request parameters](https://www.genderapi.io/docs/v2/request-parameters); [GenderAPI.io V2 responses](https://www.genderapi.io/docs/v2/responses); [GenderAPI.io V2 credits and usage](https://www.genderapi.io/docs/v2/credits-and-usage)

- [V2 request fields](https://www.genderapi.io/docs/v2/request-parameters)
- [V2 response fields](https://www.genderapi.io/docs/v2/responses)
- [Batch processing and item errors](https://www.genderapi.io/docs/v2/batch)

## 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: [GenderAPI.io accuracy methodology](https://www.genderapi.io/accuracy-methodology)

- [Our methodology and current evidence limits](https://www.genderapi.io/accuracy-methodology)
- [Dated database profile](https://www.genderapi.io/data-provenance)

## 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: [GenderAPI.io V2 authentication](https://www.genderapi.io/docs/v2/authentication); [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name)

## Will switching preserve the same output and credit cost?

No equivalence is established. Response fields, name extraction, unknown values and billing rules differ. Test your parser and cost accounting with representative cases before switching traffic.

Sources: [GenderAPI.io V2 responses](https://www.genderapi.io/docs/v2/responses); [GenderAPI.io V2 credits and usage](https://www.genderapi.io/docs/v2/credits-and-usage); [Gender-API.com FAQ: How do requests get counted?](https://gender-api.com/en/frequently-asked-questions/how-do-requests-get-counted); [Gender-API.com v2: Query by full name](https://gender-api.com/en/api-docs/v2/query-by-full-name)

## Sources and review date

- [GenderAPI.io V2 request parameters](https://www.genderapi.io/docs/v2/request-parameters): Reviewed 2026-09-26
- [GenderAPI.io V2 authentication](https://www.genderapi.io/docs/v2/authentication): Reviewed 2026-09-26
- [GenderAPI.io V2 responses](https://www.genderapi.io/docs/v2/responses): Reviewed 2026-09-26
- [GenderAPI.io V2 AI options](https://www.genderapi.io/docs/v2/ai-options): Reviewed 2026-09-26
- [GenderAPI.io V2 batch guide](https://www.genderapi.io/docs/v2/batch): Reviewed 2026-09-26
- [GenderAPI.io V2 credits and usage](https://www.genderapi.io/docs/v2/credits-and-usage): Reviewed 2026-09-26
- [GenderAPI.io accuracy methodology](https://www.genderapi.io/accuracy-methodology): Reviewed 2026-09-26
- [GenderAPI.io pricing](https://www.genderapi.io/price): Reviewed 2026-09-26
- [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-request): Reviewed 2026-09-26
- [Gender-API.com FAQ: How do requests get counted?](https://gender-api.com/en/frequently-asked-questions/how-do-requests-get-counted): Reviewed 2026-09-26
- [Gender-API.com v2: Query by email address](https://gender-api.com/en/api-docs/v2/query-by-email-address): Reviewed 2026-09-26
- [Gender-API.com v2: Query by first name](https://gender-api.com/en/api-docs/v2/query-by-first-name): Reviewed 2026-09-26
- [Gender-API.com v2: Query by full name](https://gender-api.com/en/api-docs/v2/query-by-full-name): Reviewed 2026-09-26
- [Gender-API.com official OpenAPI description](https://gender-api.com/openapi/openapi.yml): Reviewed 2026-09-26
- [Gender-API.com Python code examples](https://gender-api.com/en/code-examples/python): Reviewed 2026-09-26