shipapis
StarSubmit an APISubmit API

Numverify vs PubMed E-utilities

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

APINumverifyNEW—PubMed E-utilitiesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
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

Numverify vs PubMed E-utilities: common questions

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

On our scheduled checks, PubMed E-utilities leads on measured uptime — Numverify at —% versus PubMed E-utilities at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Numverify and PubMed E-utilities need an API key?

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

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

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

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

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