ItsThisForThat vs RSQ API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms242783
P95 · ms5551387
Authnonenone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished (docs ask you not to hammer it)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ItsThisForThat vs RSQ API: common questions

Which is more reliable, ItsThisForThat or RSQ API?

Both are neck-and-neck — ItsThisForThat 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, ItsThisForThat or RSQ API?

ItsThisForThat has the lower median latency in our checks — ItsThisForThat responds in 242 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 ItsThisForThat and RSQ API need an API key?

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

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

Are ItsThisForThat and RSQ API free for commercial use?

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