TasteDive vs JokeAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree tier — key may be requiredFree — no key
Rate limitUnpublished120 requests/minute per IP (per jokeapi.dev docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

TasteDive vs JokeAPI: common questions

Which is more reliable, TasteDive or JokeAPI?

Only JokeAPI is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do TasteDive and JokeAPI 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 TasteDive and JokeAPI 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 TasteDive and JokeAPI free for commercial use?

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