shipapis
StarSubmit an APISubmit API

AutoChangelog vs Browshot

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

APIAutoChangelogNEW—BrowshotNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AutoChangelog vs Browshot: common questions

Which is more reliable, AutoChangelog or Browshot?

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

Both ask you to authenticate — AutoChangelog uses an API key and Browshot uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call AutoChangelog and Browshot from the browser?

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

Are AutoChangelog and Browshot free for commercial use?

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