shipapis
StarSubmit an APISubmit API

VerifyEd vs Genderize.io

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

APIVerifyEdNEW—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limit100 req/window · 99 remaining · resets 1783522020Keyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

VerifyEd vs Genderize.io: common questions

Which is more reliable, VerifyEd or Genderize.io?

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

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

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

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

Are VerifyEd and Genderize.io free for commercial use?

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