RSQ API vs UrlBae

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RSQ API vs UrlBae: common questions

Which is more reliable, RSQ API or UrlBae?

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

RSQ API needs no key, while UrlBae requires a free API key. If you want to start calling without signup, reach for RSQ API first.

Can I call RSQ API and UrlBae from the browser?

Neither sends browser-friendly CORS headers reliably, so call RSQ API and UrlBae from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are RSQ API and UrlBae free for commercial use?

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