shipapis
StarSubmit an APISubmit API

OOPSpam vs OpenQR

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

APIOOPSpamHEALTHY98OpenQRHEALTHY80
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2171125
P95 · ms3602851
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?

Both are neck-and-neck — OOPSpam and OpenQR 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 OpenQR?

OOPSpam has the lower median latency in our checks — OOPSpam responds in 217 ms versus OpenQR at 1125 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 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.