PubMed E-utilities vs VerifyEd

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

Uptime · 30d
Uptime · 90d75.5%97.1%
Uptime · 30d66.7%95.0%
P50 · ms12591933
P95 · ms49033606
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit3 req/window · 1 remaining100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

PubMed E-utilities vs VerifyEd: common questions

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

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

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

PubMed E-utilities needs no key, while VerifyEd 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 VerifyEd from the browser?

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

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

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