shipapis
StarSubmit an APISubmit API

Genderize.io vs MY IP

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

APIGenderize.ioHEALTHY62MY IPDYING89
Uptime · 30d
Uptime · 90d41.2%82.4%
Uptime · 30d36.7%70.0%
P50 · ms632210
P95 · ms10601145
Authnonenone
CORSyesno
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 headersRetry-After: 721s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Genderize.io vs MY IP: common questions

Which is more reliable, Genderize.io or MY IP?

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

Which is faster, Genderize.io or MY IP?

MY IP has the lower median latency in our checks — Genderize.io responds in 632 ms versus MY IP at 210 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Genderize.io and MY IP need an API key?

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

Can I call Genderize.io and MY IP from the browser?

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

Are Genderize.io and MY IP free for commercial use?

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