shipapis
StarSubmit an APISubmit API

OpenQR vs ScreenURL

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

APIOpenQRNEW—ScreenURLNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs ScreenURL: common questions

Which is more reliable, OpenQR or ScreenURL?

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

Both ask you to authenticate — OpenQR uses an API key and ScreenURL uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call OpenQR and ScreenURL from the browser?

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

Are OpenQR and ScreenURL free for commercial use?

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