shipapis
StarSubmit an APISubmit API

ELI vs Genderize.io

Same instrument, two spec sheets — measured, not claimed.

APIELIUNMONITORED—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublishedKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

ELI vs Genderize.io: common questions

Which is more reliable, ELI or Genderize.io?

Only Genderize.io is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do ELI and Genderize.io need an API key?

Genderize.io needs no key, while ELI requires a free API key. If you want to start calling without signup, reach for Genderize.io first.

Can I call ELI and Genderize.io from the browser?

Yes — both ELI and Genderize.io send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are ELI and Genderize.io free for commercial use?

ELI has unclear commercial terms, and Genderize.io has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.