For API companies

An API reference your users' agents can actually call.

Import your OpenAPI spec. Get endpoint pages, schemas, code samples and a live console for people — and list_endpoints, get_endpoint and clean Markdown for the agents writing the integration.

The week after you sign up: A developer asks their coding agent to integrate your API. The agent lists your endpoints over MCP, reads the one it needs as Markdown, and writes working code against the version the developer runs.

How it works

  1. Import the spec. Upload or link an OpenAPI document, or build one in the editor. Refresh it when the API changes.
  2. Serve both audiences. Readers get the reference with a try-it console. Agents get the same endpoints over MCP and at .md URLs.
  3. Keep it in sync with versions. Every API belongs to a product version. Ship v2 as a complete copy; v1 stays reachable under its name.

What delivers it

OpenAPI import

Endpoint pages, schemas and samples generated from your spec.

Live console

Call the real API from the page, with auth and parameters filled in.

list_endpoints / get_endpoint

MCP tools that expose the reference to coding agents.

Product versions

Independent copies of docs and APIs per release.

Markdown reference

Every endpoint page serves clean Markdown on request.

Gap reports

Agents tell you which endpoint they couldn't find documentation for.

Other audiences: For startups · AI search visibility

Start writing for both readers.

Free while in beta. Self-hosted, your content, your database.