# I keep finding out about API breaking changes from production errors, so I'm building a changelog watcher > Source: > Published: 2026-07-23 21:20:03+00:00 I build products solo. Every single one of them sits on top of somebody else's API — Stripe for payments, OpenAI and Anthropic for AI features, Meta for ads, print-on-demand APIs, map APIs. My code is maybe half of what actually runs in production. The other half belongs to vendors, and it changes whenever they decide it changes. Twice this year the first notice I got about a breaking change was a production error. Not an email, not a warning. An error, and then me digging through the vendor's changelog trying to figure out what they changed and when. The information was public the whole time. It was sitting in a changelog page I never visit, because nobody visits changelog pages until something is on fire. BreakWatch is simple: you tell it which APIs your product depends on, and it reads their public changelogs for you. No SDK, no credentials, nothing installed in your codebase. It only reads public pages. I ran it against the real changelogs of the ten APIs I'm watching first: Stripe, Twilio, OpenAI, Anthropic, Shopify, GitHub, Slack, Cloudflare, Google Maps and Plaid. Some honest findings: It's not open for signups yet. There's a waitlist at [breakwatch.dev](https://breakwatch.dev), a live demo timeline, and a working pipeline — but no accounts and no billing, on purpose. I'm at the validation stage and I've set myself a kill condition: if the people who see this mostly say "I just subscribe to the vendor's changelog emails and that's enough," I stop building. That answer, said enough times, kills the product — and I'd rather hear it now than after building auth and billing. So I'll ask directly: Brutal honesty is the most useful thing you can leave in the comments.