shipapis
StarSubmit an APISubmit API

PubMed E-utilities vs Screenshotbase

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

APIPubMed E-utilitiesHEALTHY71ScreenshotbaseDEAD0
Uptime · 30d
Uptime · 90d70.0%0.0%
Uptime · 30d65.0%0.0%
P50 · ms348—
P95 · ms4903—
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit3 req/window · 1 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PubMed E-utilities vs Screenshotbase: common questions

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

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

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

Neither sends browser-friendly CORS headers reliably, so call PubMed E-utilities and Screenshotbase from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

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

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