Launched this week
Routebase
Catch API drift before your customers do
113 followers
Catch API drift before your customers do
113 followers
Your API lives in your design tool, your docs, your mocks, your tests, your monitoring — and every copy drifts. Routebase makes them one living source: change the spec, publish, and it catches what drifted. (Your AI agents read the same source over MCP.)
This is a real problem. Most of the time nothing actually breaks, a field just stops updating and nobody notices until the numbers look wrong weeks later. Does Routebase also catch changes in the data itself, like empty values or a new format, or only changes to the API structure?
Routebase
12 hours in — quick update: This thread has been better product feedback than most user interviews. The three most-requested things today — a turnkey GitHub Action for CI gating, first-class Slack/Teams drift alerts, and a side-by-side spec↔consumer diff — all went onto the roadmap today. Keep it coming. And my question from this morning still stands: what's the worst "the docs lied to me" moment you've had? 👇