Launching today
Routebase
Catch API drift before your customers do
94 followers
Catch API drift before your customers do
94 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 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
@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.
@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.
@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.
@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. 🙌
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
@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. 🙌
Hey Product Hunt 👋 I'm Denny, founder of Routebase.
I'm a CTO, and I built this because of what I kept watching teams go through —
not one dramatic outage, but the same slow friction on every project. The backend changes an
endpoint, and the frontend finds out from a failed integration instead of a conversation. The
docs get updated "afterwards", which means never. The frontend sits blocked, waiting for an
endpoint that's "almost done". And the API counts as "tested" because there are unit tests
around the handler — but nobody has actually checked that what runs in production still matches
the contract everyone coded against.
None of that is one team's fault. It's structural: design, docs, mocks, tests, monitoring — each
tool quietly keeps its own copy of the API, and the copies drift the moment you ship a change.
The pain happens between the tools, so no single point tool can fix it.
Routebase is the one living source they all derive from. You design the API once; your docs, doc
portals, mock server, contract tests, and monitoring come from that same spec. The frontend codes
against the mock from day one instead of waiting for the backend. And when you change the spec
and publish, Routebase catches what drifted. My favorite moment in the demo: I add one required
field to a schema, publish, and a contract test runs against the live API and goes red — a
breaking change caught before a single consumer saw it, and before the frontend lost a day to it.
(And the part I quietly love: your AI agents read that same source over MCP — so the agent answers
from the real API, instead of becoming one more drifting copy of it.)
Routebase v1 is live today: API design, auto-generated docs, contract testing, mock servers,
monitoring, and governance — one source of truth for the whole lifecycle.
I'd genuinely love your feedback — especially if you've lived the backend↔frontend standoff.
What's the worst "the docs lied to me" moment you've had? I'll be here all day. 🙏
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.
@muhammedjbxo thanks so much — really glad it's clicking, especially the MCP side 🙏