ELI vs OpenQR

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms5911125
P95 · ms18172851
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ELI vs OpenQR: common questions

Which is more reliable, ELI or OpenQR?

On our scheduled checks, OpenQR leads on measured uptime — ELI at 99.02% versus OpenQR at 100% 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, ELI or OpenQR?

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

Both ask you to authenticate — ELI 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 ELI and OpenQR from the browser?

Yes — both ELI 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 ELI and OpenQR free for commercial use?

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