shipapis
StarSubmit an APISubmit API

Excuser vs kimiquotes

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

APIExcuserNEW—kimiquotesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Excuser vs kimiquotes: common questions

Which is more reliable, Excuser or kimiquotes?

On our scheduled checks, kimiquotes leads on measured uptime — Excuser 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 Excuser and kimiquotes need an API key?

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

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

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