shipapis
StarSubmit an APISubmit API

JokeAPI vs TasteDive

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

APIJokeAPIHEALTHY98TasteDiveHEALTHY95
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms224325
P95 · ms8842265
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?

Both are neck-and-neck — JokeAPI and TasteDive 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, JokeAPI or TasteDive?

JokeAPI has the lower median latency in our checks — JokeAPI responds in 224 ms versus TasteDive at 325 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 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.