shipapis
StarSubmit an APISubmit API

npm Registry vs Genderize.io

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

APInpm RegistryNEW—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (public registry)Keyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublished (bulk scraping discouraged)Keyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

npm Registry vs Genderize.io: common questions

Which is more reliable, npm Registry or Genderize.io?

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

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

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

npm Registry 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.