Browshot vs Catchdoms Security API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnono
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 Catchdoms Security API: common questions

Which is more reliable, Browshot or Catchdoms Security API?

On our scheduled checks, Catchdoms Security API leads on measured uptime — Browshot at —% versus Catchdoms Security API 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 Catchdoms Security API need an API key?

Catchdoms Security API needs no key, while Browshot requires a free API key. If you want to start calling without signup, reach for Catchdoms Security API first.

Can I call Browshot and Catchdoms Security API from the browser?

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

Are Browshot and Catchdoms Security API free for commercial use?

Browshot has unclear commercial terms, and Catchdoms Security API 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.