AutoChangelog vs GeoScore

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
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 GeoScore: common questions

Which is more reliable, AutoChangelog or GeoScore?

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

Both ask you to authenticate — AutoChangelog uses an API key and GeoScore 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 GeoScore from the browser?

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

Are AutoChangelog and GeoScore free for commercial use?

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