Browshot vs restful-api.dev

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Browshot vs restful-api.dev: common questions

Which is more reliable, Browshot or restful-api.dev?

On our scheduled checks, restful-api.dev leads on measured uptime — Browshot at —% versus restful-api.dev 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 Browshot and restful-api.dev need an API key?

restful-api.dev needs no key, while Browshot requires a free API key. If you want to start calling without signup, reach for restful-api.dev first.

Can I call Browshot and restful-api.dev from the browser?

Only restful-api.dev is browser-friendly — it returns CORS headers over HTTPS. Browshot needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Browshot and restful-api.dev free for commercial use?

Browshot has unclear commercial terms, and restful-api.dev 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.