icanhazdadjoke vs justmeme.wtf

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms222776
P95 · ms15561501
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limit100 req/window · 98 remaining · resets 178351391360 requests/minute per IP (per docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

icanhazdadjoke vs justmeme.wtf: common questions

Which is more reliable, icanhazdadjoke or justmeme.wtf?

On our scheduled checks, justmeme.wtf leads on measured uptime — icanhazdadjoke at 99.02% versus justmeme.wtf 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, icanhazdadjoke or justmeme.wtf?

icanhazdadjoke has the lower median latency in our checks — icanhazdadjoke responds in 222 ms versus justmeme.wtf at 776 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 icanhazdadjoke and justmeme.wtf need an API key?

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

Can I call icanhazdadjoke and justmeme.wtf from the browser?

Yes — both icanhazdadjoke and justmeme.wtf 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 icanhazdadjoke and justmeme.wtf free for commercial use?

icanhazdadjoke has unclear commercial terms, and justmeme.wtf 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.