ClarifyThe autonomous CRM that helps you sell more
Promoted
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.)
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.
Routebase
@didem2rjr you're right that it's harder to see than it should be. the field-level diff actually is in the publish step — which endpoint, which field, old vs new — but today it's tucked behind a "View Full Diff" click, and the "drift detected" notification you're seeing is way too bare (it should link you straight to what moved). surfacing the exact fields right where you first land is exactly where we're taking it. thanks for calling it out 🙏
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
Routebase
@zekiyehwuy Thank you! Catching two stale params you'd missed for weeks is exactly the kind of thing we want the diff view + MCP to surface. Really glad it's paying off for your team. 🙌
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.
Routebase
@fatmaburkal9ee Thank you! Three mocks and a test going stale without anyone noticing is the exact nightmare we built this to end — glad one schema tweak surfaced all of it for you. 🙌
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.
Routebase
@sevilgwkc Great suggestion. Quick tip in the meantime: click "Review changes" on any drifted mock/doc/test and you'll get a field-level breakdown (path + old → new value), so you can already see exactly what shifted rather than just the alert. A true side-by-side spec-vs-consumer panel isn't there yet though — I like it, noting it down. 🙏
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.
Routebase
@zehraasnf Thank you! Catching two out-of-sync doc endpoints before a release is exactly the headache we want to spare you — glad it paid off right away. 🙌
Macaly
api drift is such an underrated pain. nice wedge 🙌 does it cover graphql too?
Routebase
@petrkovacik Thanks! 🙌 Honest answer: not yet. The drift engine is OpenAPI/REST today — GraphQL only shows up as a dependency-type label in the service catalog, not as a modeled, drift-checked schema. GraphQL SDL drift is a really natural next axis though — noting it down. 🙏
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
Routebase
@leventgzaygdkz Thank you! Killing the "wait, why did this break" moments is exactly why MCP pulls live spec updates instead of a stale copy — glad that detail lands for you. 🙌