shipapis
StarSubmit an APISubmit API

icanhazdadjoke vs Agify

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

APIicanhazdadjokeNEW—AgifyHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedProprietary
Free tierFree — limits not published100 names/day, no signup
Rate limit100 req/window · 98 remaining · resets 1783513913100/day per IP
In directory since2026-07-052026-05-02
operationalpartialdownno data

icanhazdadjoke vs Agify: common questions

Which is more reliable, icanhazdadjoke or Agify?

On our scheduled checks, Agify leads on measured uptime — icanhazdadjoke 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 icanhazdadjoke and Agify need an API key?

Neither needs a paid key — icanhazdadjoke 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 icanhazdadjoke and Agify from the browser?

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

icanhazdadjoke 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.