shipapis
StarSubmit an APISubmit API

PubMed E-utilities vs serpstack

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

APIPubMed E-utilitiesHEALTHY68serpstackHEALTHY93
Uptime · 30d
Uptime · 90d75.5%99.02%
Uptime · 30d66.7%98.3%
P50 · ms1259492
P95 · ms49031442
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limit3 req/window · 1 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PubMed E-utilities vs serpstack: common questions

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

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

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

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

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

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

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

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