QR & Barcode vs Spoo.me

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

QR & Barcode vs Spoo.me: common questions

Which is more reliable, QR & Barcode or Spoo.me?

On our scheduled checks, Spoo.me leads on measured uptime — QR & Barcode at —% versus Spoo.me 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 QR & Barcode and Spoo.me need an API key?

Neither needs a paid key — QR & Barcode is callable with no signup, and Spoo.me is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call QR & Barcode and Spoo.me from the browser?

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

Are QR & Barcode and Spoo.me free for commercial use?

QR & Barcode has unclear commercial terms, and Spoo.me 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.