shipapis
StarSubmit an APISubmit API

RSQ API vs Genderize.io

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

APIRSQ APIUNMONITORED—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSnoyes
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

RSQ API vs Genderize.io: common questions

Which is more reliable, RSQ API 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 RSQ API and Genderize.io need an API key?

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

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

Are RSQ API and Genderize.io free for commercial use?

RSQ API 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.