shipapis
StarSubmit an APISubmit API

OOPSpam vs OpenQR

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

APIOOPSpamNEW—OpenQRNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limit1000 req/window · 999 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OOPSpam vs OpenQR: common questions

Which is more reliable, OOPSpam or OpenQR?

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

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

Can I call OOPSpam and OpenQR from the browser?

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

Are OOPSpam and OpenQR free for commercial use?

OOPSpam has unclear commercial terms, and OpenQR 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.