shipapis
StarSubmit an APISubmit API

ParlayAPI vs PubMed E-utilities

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

APIParlayAPIREACHABLE88PubMed E-utilitiesHEALTHY71
Uptime · 30d
Uptime · 90d87.5%70.0%
Uptime · 30d87.5%65.0%
P50 · ms211348
P95 · ms15364903
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limit3 req/window · 1 remaining
In directory since2026-10-042026-07-05
operationalpartialdownno data

ParlayAPI vs PubMed E-utilities: common questions

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

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

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

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

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

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

Are ParlayAPI and PubMed E-utilities free for commercial use?

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