Genderize.io vs Keyvalue

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

Uptime · 30d
Uptime · 90d49.4%92.1%
Uptime · 30d58.6%100%
P50 · ms287427
P95 · ms10603359
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 Keyvalue: common questions

Which is more reliable, Genderize.io or Keyvalue?

On our scheduled checks, Keyvalue leads on measured uptime — Genderize.io at 49.4% versus Keyvalue at 92.1% 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 Keyvalue?

Genderize.io has the lower median latency in our checks — Genderize.io responds in 287 ms versus Keyvalue at 427 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 Keyvalue need an API key?

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

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

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

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