shipapis
StarSubmit an APISubmit API

Audexum vs OpenQR

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

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

Audexum vs OpenQR: common questions

Which is more reliable, Audexum or OpenQR?

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

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

Yes — both Audexum and OpenQR send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Audexum and OpenQR free for commercial use?

Audexum 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.