shipapis
StarSubmit an APISubmit API

Genderize.io vs IPGeolocation

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

APIGenderize.ioNEW—IPGeolocationREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
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 — 1000 requests/day
Rate limitKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

Genderize.io vs IPGeolocation: common questions

Which is more reliable, Genderize.io or IPGeolocation?

On our scheduled checks, IPGeolocation leads on measured uptime — Genderize.io at —% versus IPGeolocation 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 IPGeolocation need an API key?

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

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

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

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