shipapis
StarSubmit an APISubmit API

OpenQR vs Render API

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

APIOpenQRNEW—Render APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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 Render API: common questions

Which is more reliable, OpenQR or Render API?

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

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

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

Are OpenQR and Render API free for commercial use?

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