Affirmations.dev vs icanhazdadjoke

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms590222
P95 · ms10811556
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished100 req/window · 98 remaining · resets 1783513913
In directory since2026-07-052026-07-05
operationalpartialdownno data

Affirmations.dev vs icanhazdadjoke: common questions

Which is more reliable, Affirmations.dev or icanhazdadjoke?

On our scheduled checks, Affirmations.dev leads on measured uptime — Affirmations.dev at 100% versus icanhazdadjoke at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Affirmations.dev or icanhazdadjoke?

icanhazdadjoke has the lower median latency in our checks — Affirmations.dev responds in 590 ms versus icanhazdadjoke at 222 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Affirmations.dev and icanhazdadjoke need an API key?

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

Can I call Affirmations.dev and icanhazdadjoke from the browser?

Only icanhazdadjoke is browser-friendly — it returns CORS headers over HTTPS. Affirmations.dev needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Affirmations.dev and icanhazdadjoke free for commercial use?

Affirmations.dev has unclear commercial terms, and icanhazdadjoke 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.