shipapis
StarSubmit an APISubmit API

Yes-as-a-Service vs Genderize.io

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

APIYes-as-a-ServiceUNMONITORED—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
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

Yes-as-a-Service vs Genderize.io: common questions

Which is more reliable, Yes-as-a-Service or Genderize.io?

Only Genderize.io is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Yes-as-a-Service and Genderize.io need an API key?

Neither needs a paid key — Yes-as-a-Service 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 Yes-as-a-Service and Genderize.io from the browser?

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

Yes-as-a-Service 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.