DummyJSON vs OpenQR

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms321125
P95 · ms11132851
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree tier — key may be required
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs OpenQR: common questions

Which is more reliable, DummyJSON or OpenQR?

On our scheduled checks, OpenQR leads on measured uptime — DummyJSON 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, DummyJSON or OpenQR?

DummyJSON has the lower median latency in our checks — DummyJSON responds in 32 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 DummyJSON and OpenQR need an API key?

DummyJSON needs no key, while OpenQR requires a free API key. If you want to start calling without signup, reach for DummyJSON first.

Can I call DummyJSON and OpenQR from the browser?

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

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