Routebase

Catch API drift before your customers do

API

SaaS

Developer Tools

Visit WebsiteSee on Product HuntTwitter ⧉LinkedIn ⧉

the request/response drift coverage in this thread is thorough. one direction I didn't see covered: outbound webhooks. those break consumers just as often as REST responses do, but there's no request to inspect, just whatever payload you decide to send on an event. is webhook payload schema part of the same spec/drift pipeline, or is that a separate problem you're leaving to the consumer to validate on their end?

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.

honestly the drift detection part is what pulled me in, super useful. one thing though, it would be amazing if you could add some kind of slack or teams alert when drift actually gets caught in prod, so the right person gets pinged right away instead of someone having to go check the dashboard. would save a lot of "wait when did this break" moments.

finally something that tackles the spec drift problem head on. hooked up our openapi and it immediately flagged two endpoints in our docs that were out of sync, which honestly saved me a headache before our next release.

love that the MCP angle means my agents actually pick up the same spec updates instead of working off last week's version — that detail alone saves a ton of "wait why did this break" moments

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.

The drift-detection angle is genuinely useful, most teams I know are drowning in stale API docs that nobody trusts anymore. Love that it hooks into MCP so agents stay in sync too.

Drift detection sounds great, but it would help a lot if Routebase could show a side-by-side diff view between the published spec and each consumer like the docs or mocks so I can spot what changed at a glance instead of just getting a list of drift alerts.

Finally something that ends the API doc drift nightmare for me. I tweaked a schema on Monday and it actually caught three mocks and a test that had gone stale without me noticing for weeks.

finally a way to stop the endless api drift between figma and our actual endpoints, the mcp piece is slick and the diff view caught two stale params we'd missed for weeks

A diff view inside the publishing step would be huge so I can see exactly which endpoint fields changed before pushing the update live. Right now it just says "drift detected" but I have to hunt to figure out what actually moved.

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.

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.

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.

Finally a tool that gets at the actual pain of API drift. I poked around and the MCP piece is genuinely useful since my agents were always pulling from stale docs.

Honestly the MCP angle is what got me, I hooked our docs up and it actually flagged two stale endpoints we had been ignoring for months. Kind of wish the publish step was faster but the drift catching alone makes it worth using.

love that it actually catches drift across mocks, tests, and docs instead of just generating them separately. the MCP piece is smart too, basically lets agents stay in sync without a ton of glue code.

Would love to see a visual diff view for breaking changes before publishing the spec update, so we can quickly show backend and frontend teams what exactly shifted instead of just flagging drift.

spent an afternoon hooking it up to our openapi spec and it actually caught two stale routes in our docs i didn't know were drifting. the MCP bit for our agents is genuinely handy too.