Abstract API vs PubMed E-utilities

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

Uptime · 30d
Uptime · 90d99.02%75.5%
Uptime · 30d98.3%66.7%
P50 · ms7001259
P95 · ms16564903
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublished3 req/window · 1 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Abstract API vs PubMed E-utilities: common questions

Which is more reliable, Abstract API or PubMed E-utilities?

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

Abstract API has the lower median latency in our checks — Abstract API responds in 700 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 Abstract API and PubMed E-utilities need an API key?

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

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

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

Abstract API 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.