What changes between these APIs?
Genderize documents a compact name-focused GET interface. GenderAPI.io V2 combines names, emails and usernames in one request model with explicit AI modes. Choose by your input workflow and evidence requirements; this comparison does not identify an accuracy winner.
| Decision point | GenderAPI.io V2 | Genderize.io | Sources |
|---|---|---|---|
| Inputs and country | Names, email addresses and usernames use type and value on /api/v2/gender. Optional country supplies context. | First or full name via name; country_id adds country context. Dedicated email and username inputs are not documented in this reference. | [1][11] |
| Authentication | Authorization: Bearer with a GenderAPI.io key. Query keys are available for simple GET examples; prefer headers in applications. | apikey in the query string of GET https://api.genderize.io. | [2][11] |
| Batch requests | Up to 50 keyed items or 10 IP-trial items. Each item can have its own type, country and options. | Repeated name[] parameters; up to 100 names with one country_id. | [5][11] |
| 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. | gender may be null. probability is 0–1; count reports evidence count. | [3][11] |
| AI routing | Explicit off, fallback or always. Singles default to fallback; batches default to off. Optional forceToGenderize uses the dataset first, then nickname-aware AI. | Request-level AI controls are not documented in the reviewed reference. | [4][11] |
| Usage accounting | 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. | Plans count each name, including names within a batch. Monthly allowances reset. | [6][10] |
Before you switch an integration
Change the URL, credential and request parser together. Map name to type: name plus value, and country_id to country. Read data.gender instead of a top-level gender field. Split 100-name batches to the V2 limit. Select options.ai_mode explicitly so switching providers does not silently enable a different inference path.
Even where probability and confidence share a 0–1 scale, their evidence and thresholds are not interchangeable. Preserve unknowns and inspect confidence_kind before using a score in application logic.
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
Does this comparison show which API is more accurate?
No. Genderize publishes provider-run evaluations, but this review did not rerun them or test GenderAPI.io V2 on the same labelled sample. Use those studies as methodological evidence, not a cross-provider ranking.
Can I reuse my Genderize key with GenderAPI.io?
No. These are separate services with separate accounts. Use your GenderAPI.io key and verify meta.access.mode is api_key; missing or unrecognized keys can fall back to the shared IP trial.
Sources:[2]
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
- How Accurate Is Genderize? Open Benchmarkshttps://genderize.io/our-dataReviewed
- Pricing and plans for Genderize.iohttps://genderize.io/pricingReviewed
- Gender API referencehttps://genderize.io/documentation/api/referenceReviewed