JokeAPI vs TasteDive

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project)Unverified
Free tierFree — no keyFree tier — key may be required
Rate limit120 requests/minute per IP (per jokeapi.dev docs)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

JokeAPI vs TasteDive: common questions

Which is more reliable, JokeAPI or TasteDive?

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

JokeAPI needs no key, while TasteDive requires a free API key. If you want to start calling without signup, reach for JokeAPI first.

Can I call JokeAPI and TasteDive from the browser?

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

Are JokeAPI and TasteDive free for commercial use?

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