kimiquotes vs JokeAPI

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

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

kimiquotes vs JokeAPI: common questions

Which is more reliable, kimiquotes 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 kimiquotes and JokeAPI need an API key?

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

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

Are kimiquotes and JokeAPI free for commercial use?

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