shipapis
StarSubmit an APISubmit API

OOPSpam vs RSQ API

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

APIOOPSpamHEALTHY98RSQ APIHEALTHY91
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms217783
P95 · ms3601387
Authnonenone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit1000 req/window · 999 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OOPSpam vs RSQ API: common questions

Which is more reliable, OOPSpam or RSQ API?

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

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

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

Neither sends browser-friendly CORS headers reliably, so call OOPSpam 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 OOPSpam and RSQ API free for commercial use?

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