Routebase keeps your docs, mocks, and tests in sync with your API

Routebase is an API design, testing, and documentation platform built on one living OpenAPI spec. You design the contract in a visual editor, and the mock server, the test suites, and the published docs derive from that same spec, so they stay in sync when the API changes. A built-in MCP server lets agents work the same spec under your team's permissions.

Yes, because an agent makes it cheap to change an API, so the docs, mocks, and tests drift apart faster than anyone can check by hand. A generated test or doc page reads plausibly, but it doesn't tell you whether it still matches the API that's live. Routebase keeps one living spec as the single source of truth, and a contract test turns red when your live API stops matching it. Your agents run those tests themselves through the built-in MCP server, so they see what failed and fix it before anyone reviews the change. Because every docs portal also serves llms.txt and Markdown, the agents that call your API read the same contract as your team.

Every new account starts on a full Pro trial — all features unlocked for 14 days. No credit card and no plan selection; the trial starts the moment you sign up.

Your workspace automatically moves to the Free plan. Nothing is deleted — projects, specs, and history are retained, and you can upgrade any time to pick up where you left off.

No. You only enter payment details when you choose a paid plan.

You choose EU or US data residency when you sign up, and your workspace stays in that region. Both regions run on Microsoft Azure.

How data residency works →

You don't need one to start. Create an empty specification and add endpoints in the visual editor, or begin from a CRUD or auth template — Routebase writes the OpenAPI for you as you go. Testing needs no spec at all: a test case is a plain HTTP request, and linking it to an endpoint is optional. Most APIs arrive here undocumented; the spec is what you leave with, not what you bring.

Yes — import OpenAPI specs directly, or bring collections from Postman or Insomnia; example request bodies become schemas on the way in. No file at all? Start from an empty spec or a template. From there, your spec is the single source of truth.

Yes. A test case is a plain HTTP request with the auth scheme the endpoint needs — ten schemes, from Bearer and API key to OAuth2 and AWS SigV4. Assertions are declarative: six types (status, body, header, JSON path, latency, schema) with ten operators, so there are no test scripts to maintain when the team changes. Chain cases into scenarios that pass extracted values downstream, run a suite once per row of a data set, put it on a cron schedule, or gate CI with the CLI and GitHub Action. OWASP API Top 10 scanning ships alongside, with a CI gate of its own. A Postman or Insomnia collection imports as a specification, and one click generates a test case per endpoint from it. None of it requires an OpenAPI spec to begin with.

Every workspace exposes a built-in MCP server. Agents like Claude or Cursor discover your APIs as tools and can design, lint, and test specs — under the same permissions as your team.

Yes. Enterprise starts at 25 seats and you subscribe directly in the app — SAML SSO, SCIM, and audit log export included. No sales call required.

Yes. Starter, Pro, and Enterprise are listed on Microsoft Marketplace at the same USD list prices, billed by Microsoft on your existing account and shown in your local currency. Starter and Pro include the 14-day free trial there too; the Free plan is available directly on routebase.dev.

How buying through Microsoft works →

Yes, in one click. Your plan stays active until the end of the billing period, then the workspace downgrades to Free with all data retained.