Bacon Ipsum vs RSQ API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bacon Ipsum vs RSQ API: common questions

Which is more reliable, Bacon Ipsum or RSQ API?

On our scheduled checks, RSQ API leads on measured uptime — Bacon Ipsum at —% versus RSQ API 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 Bacon Ipsum and RSQ API need an API key?

Neither needs a paid key — Bacon Ipsum 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 Bacon Ipsum and RSQ API from the browser?

Only Bacon Ipsum 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 Bacon Ipsum and RSQ API free for commercial use?

Bacon Ipsum 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.