shipapis
StarSubmit an APISubmit API

ip-api.com vs Genderize.io

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

APIip-api.comNEW—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless 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

ip-api.com vs Genderize.io: common questions

Which is more reliable, ip-api.com or Genderize.io?

On our scheduled checks, Genderize.io leads on measured uptime — ip-api.com 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 ip-api.com and Genderize.io need an API key?

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

Can I call ip-api.com and Genderize.io from the browser?

Only Genderize.io is browser-friendly — it returns CORS headers over HTTPS. ip-api.com needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ip-api.com and Genderize.io free for commercial use?

ip-api.com 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.