shipapis
StarSubmit an APISubmit API

Genderize.io vs InternetDB API

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

APIGenderize.ioNEW—InternetDB APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free keyFree — limits not published
Rate limitKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headersUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Genderize.io vs InternetDB API: common questions

Which is more reliable, Genderize.io or InternetDB API?

On our scheduled checks, InternetDB API leads on measured uptime — Genderize.io at —% versus InternetDB API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Genderize.io and InternetDB API need an API key?

Neither needs a paid key — Genderize.io is callable with no signup, and InternetDB API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Genderize.io and InternetDB API from the browser?

Yes — both Genderize.io and InternetDB API 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 Genderize.io and InternetDB API free for commercial use?

Genderize.io has unclear commercial terms, and InternetDB API 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.