chucknorris.io vs Agify

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedProprietary
Free tierFree, no key100 names/day, no signup
Rate limitUnpublished100/day per IP
In directory since2026-07-052026-05-02
operationalpartialdownno data

chucknorris.io vs Agify: common questions

Which is more reliable, chucknorris.io or Agify?

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

Neither needs a paid key — chucknorris.io is callable with no signup, and Agify is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call chucknorris.io and Agify from the browser?

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

chucknorris.io has unclear commercial terms, and Agify allows commercial use on its free tier. 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.