shipapis
StarSubmit an APISubmit API

Genderize.io vs GeoScore

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

APIGenderize.ioNEW—GeoScoreNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
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 tier — API key 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 GeoScore: common questions

Which is more reliable, Genderize.io or GeoScore?

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

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

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

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

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