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.)
Routebase
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. 🙏
Routebase
That's a wrap — thank you, Product Hunt 🙏
We finished the day at #15 with 106 new followers — but the real result is this comment thread. You asked sharper questions than most user interviews produce, and you found the honest edges of the product faster than any audit we've run.
What you changed in one day — all of these went from "comment in this thread" to scoped roadmap items:
— A turnkey CI check (GitHub Action) to gate builds on breaking-change diffs and contract tests
— First-class Slack/Teams drift alerts — the right person gets pinged, not a dashboard nobody's watching
— A side-by-side spec↔consumer diff — preview the blast radius before you publish, not after
— Webhook/event payload contracts — outbound payloads get the same doc/mock/test/drift treatment as REST responses
— A typed client/SDK generator, one step up from per-request snippets
Special thanks to those of you who pushed past the demo answers — the questions about unannounced drift, auth-failure vs. schema-drift signals, and the webhook gap made the product better this week, not "someday."
If you missed the day: the launch deal (30% off for 3 months) is still live for a bit, and I'm still answering everything — here or in p/routebase. And my favorite question of the day still stands: what's the worst "the docs lied to me" moment you've ever had? I read every answer. 👋
Cheers, Denny
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.
Routebase
@muhammedjbxo thanks so much — really glad it's clicking, especially the MCP side 🙏
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.
Routebase
@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.
Routebase
@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.
Routebase
@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.
Routebase
@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.