shipapis
StarSubmit an APISubmit API

Affirmations.dev vs JokeAPI

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

APIAffirmations.devHEALTHY92JokeAPIHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms590224
P95 · ms1081884
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree — limits not publishedFree — no key
Rate limitUnpublished120 requests/minute per IP (per jokeapi.dev docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Affirmations.dev vs JokeAPI: common questions

Which is more reliable, Affirmations.dev or JokeAPI?

Both are neck-and-neck — Affirmations.dev and JokeAPI each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Affirmations.dev or JokeAPI?

JokeAPI has the lower median latency in our checks — Affirmations.dev responds in 590 ms versus JokeAPI at 224 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 JokeAPI need an API key?

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

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

Only JokeAPI 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 JokeAPI free for commercial use?

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