Routebase
Catch API drift before your customers do
117 followers
Catch API drift before your customers do
117 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.)
Finally tried this on a messy internal API setup and the drift detection caught two stale endpoints we totally missed. The MCP piece feels like the real unlock for our coding agents.
Routebase
@sraaf2l Thank you! Two stale endpoints you'd totally missed is exactly the catch we're after — and hearing MCP feels like the unlock for your coding agents means a lot, that's precisely the bet we made. 🙌
Really like this problem to solve.
I'm curious whether customers usually discover API drift after something breaks, or are you seeing teams adopt Routebase proactively before incidents happen?
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? 👇