shipapis
StarSubmit an APISubmit API

Metropolitan Museum of Art vs Screenshotlayer

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

APIMetropolitan Museum of ArtNEW—ScreenshotlayerNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC0 1.0 (Open Access data)Unverified
Free tierFree, no API key requiredFree — limits not published
Rate limit80 requests/second (requested in docs)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metropolitan Museum of Art vs Screenshotlayer: common questions

Which is more reliable, Metropolitan Museum of Art or Screenshotlayer?

On our scheduled checks, Screenshotlayer leads on measured uptime — Metropolitan Museum of Art at —% versus Screenshotlayer 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 Metropolitan Museum of Art and Screenshotlayer need an API key?

Neither needs a paid key — Metropolitan Museum of Art is callable with no signup, and Screenshotlayer is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Metropolitan Museum of Art and Screenshotlayer from the browser?

Only Metropolitan Museum of Art is browser-friendly — it returns CORS headers over HTTPS. Screenshotlayer needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Metropolitan Museum of Art and Screenshotlayer free for commercial use?

Metropolitan Museum of Art allows commercial use on its free tier, and Screenshotlayer 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.