shipapis
StarSubmit an APISubmit API

Dev.to vs Genderize.io

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

APIDev.toNEW—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

Dev.to vs Genderize.io: common questions

Which is more reliable, Dev.to or Genderize.io?

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

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

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

Dev.to 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.