shipapis
StarSubmit an APISubmit API

OpenQR vs PubMed E-utilities

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

APIOpenQRHEALTHY80PubMed E-utilitiesHEALTHY68
Uptime · 30d
Uptime · 90d100%75.5%
Uptime · 30d100%66.7%
P50 · ms11251259
P95 · ms28514903
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublished3 req/window · 1 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs PubMed E-utilities: common questions

Which is more reliable, OpenQR or PubMed E-utilities?

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

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

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

Can I call OpenQR and PubMed E-utilities from the browser?

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

OpenQR has unclear commercial terms, and PubMed E-utilities 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.