shipapis
StarSubmit an APISubmit API

IPGeolocation vs Genderize.io

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

APIIPGeolocationREACHABLE—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limit1000 requests/day on free planKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs Genderize.io: common questions

Which is more reliable, IPGeolocation or Genderize.io?

On our scheduled checks, Genderize.io leads on measured uptime — IPGeolocation at —% versus Genderize.io 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 IPGeolocation and Genderize.io 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 IPGeolocation and Genderize.io from the browser?

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

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