OpenQR vs YADG

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

Uptime · 30d
Uptime · 90d100%2.9%
Uptime · 30d100%0.0%
P50 · ms11251308
P95 · ms28511359
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 YADG: common questions

Which is more reliable, OpenQR or YADG?

On our scheduled checks, OpenQR leads on measured uptime — OpenQR at 100% versus YADG at 2.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, OpenQR or YADG?

OpenQR has the lower median latency in our checks — OpenQR responds in 1125 ms versus YADG at 1308 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 OpenQR and YADG need an API key?

Both ask you to authenticate — OpenQR uses an API key and YADG 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 YADG from the browser?

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

Are OpenQR and YADG free for commercial use?

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