shipapis
StarSubmit an APISubmit API

Kroki vs RSQ API

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

APIKrokiHEALTHY92RSQ APIHEALTHY91
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms633783
P95 · ms31831387
Authnonenone
CORSyesyes
HTTPSyesno
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

Kroki vs RSQ API: common questions

Which is more reliable, Kroki or RSQ API?

Both are neck-and-neck — Kroki and RSQ API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Kroki or RSQ API?

Kroki has the lower median latency in our checks — Kroki responds in 633 ms versus RSQ API at 783 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 Kroki and RSQ API need an API key?

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

Can I call Kroki and RSQ API from the browser?

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

Are Kroki and RSQ API free for commercial use?

Kroki has unclear commercial terms, and RSQ API 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.