shipapis
StarSubmit an APISubmit API

justmeme.wtf vs kimiquotes

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

APIjustmeme.wtfNEW—kimiquotesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limit60 requests/minute per IP (per docs)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

justmeme.wtf vs kimiquotes: common questions

Which is more reliable, justmeme.wtf or kimiquotes?

On our scheduled checks, kimiquotes leads on measured uptime — justmeme.wtf at —% versus kimiquotes at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do justmeme.wtf and kimiquotes need an API key?

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

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

Only justmeme.wtf 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 justmeme.wtf and kimiquotes free for commercial use?

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