OpenQR vs PageBolt

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2356279
P95 · ms49871314
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 PageBolt: common questions

Which is more reliable, OpenQR or PageBolt?

Both are neck-and-neck — OpenQR and PageBolt 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, OpenQR or PageBolt?

PageBolt has the lower median latency in our checks — OpenQR responds in 2356 ms versus PageBolt at 279 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 PageBolt need an API key?

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

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

Are OpenQR and PageBolt free for commercial use?

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