Geek Jokes vs JokeAPI

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

Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d98.3%100%
P50 · ms357142
P95 · ms1048884
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree, no API key requiredFree — no key
Rate limitUnpublished120 requests/minute per IP (per jokeapi.dev docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geek Jokes vs JokeAPI: common questions

Which is more reliable, Geek Jokes or JokeAPI?

On our scheduled checks, JokeAPI leads on measured uptime — Geek Jokes at 99.44% versus JokeAPI at 100% 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, Geek Jokes or JokeAPI?

JokeAPI has the lower median latency in our checks — Geek Jokes responds in 357 ms versus JokeAPI at 142 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 Geek Jokes and JokeAPI need an API key?

Neither needs a paid key — Geek Jokes 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 Geek Jokes and JokeAPI from the browser?

Yes — both Geek Jokes and JokeAPI send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Geek Jokes and JokeAPI free for commercial use?

Geek Jokes 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.