shipapis
StarSubmit an APISubmit API

Genderize.io vs Numverify

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

APIGenderize.ioHEALTHY62NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d41.2%100%
Uptime · 30d36.7%100%
P50 · ms632449
P95 · ms10601488
AuthnoneapiKey
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 tier — key may be required
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 Numverify: common questions

Which is more reliable, Genderize.io or Numverify?

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

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

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

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

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

Are Genderize.io and Numverify free for commercial use?

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