Launching today
Routebase
Catch API drift before your customers do
99 followers
Catch API drift before your customers do
99 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 something that tackles the copy drift problem head on. Tested it on a small endpoints project and watching it flag a stale response example in the docs was genuinely satisfying.
@etinkocako7yqn Thanks so much — really glad it clicked for you! 🙌
honestly the drift catching is what got me, like i updated one endpoint and it flagged two stale mocks i forgot about. saves me from those awkward "works on my end" moments.
@diyarkmdwjr thanks so much — killing the "works on my end" moment is exactly what we're here for 🙏
The drift detection actually works. I tweaked one endpoint and it flagged a mock and a test that were both out of sync within seconds, which is exactly the kind of thing I usually find weeks later. Nice that AI agents can read the same source too.
@alperenkkkbb2y thank you 🙏 catching it in seconds instead of weeks later is exactly the point
Finally tried routebase on a messy node project and it caught three routes that drifted between our swagger doc and tests, exactly the kind of thing that always sneaks past review. The MCP angle is genuinely useful too since our agents can pull the same source.
@metehaneniknjo Thank you! Routes quietly drifting past review is exactly the leak we built this to close — glad it surfaced three on a real project.
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.
@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. 🙌
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? 👇
Finally something that actually tackles the spec drift problem instead of just complaining about it. The MCP piece is clever too, now my agents read the same source as my docs.
@esilape7l Thank you, honestly means a lot 🙏