shipapis
StarSubmit an APISubmit API

PubMed E-utilities vs ReportForge

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

APIPubMed E-utilitiesNEW—ReportForgeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit3 req/window · 1 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PubMed E-utilities vs ReportForge: common questions

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

On our scheduled checks, ReportForge leads on measured uptime — PubMed E-utilities at —% versus ReportForge 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 PubMed E-utilities and ReportForge need an API key?

Neither needs a paid key — PubMed E-utilities is callable with no signup, and ReportForge is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

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

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