API docs

API docs people and agents can read.

Let your agent write them from your code, or import OpenAPI or Postman. Publish a fast reference with a built-in playground, and get an MCP server and CLI from the same docs.

one source, every reader
docs.acme.com            for people
docs.acme.com/llms.txt   for models
docs.acme.com/x.md       for agents
mcp.acme.com             for agents
openapi.json             for tools
docstar-cli acme         for terminals

The reference

Everything a public API reference needs.

Without running a separate docs site.

  • Written by your agent

    Your coding agent reads your routes and creates every endpoint, with auth, params, bodies and responses. No OpenAPI file needed.

  • Or import a spec

    Bring OpenAPI 3, Swagger 2 or a Postman collection and get a structured reference.

  • Try it in the docs

    Readers send real requests with params, headers, body and auth, right from the page.

  • Environments

    Switch base URLs and variables between sandbox and production.

  • Guides and changelogs

    Getting-started guides and API changelogs live with the reference.

  • Search and AI answers

    Readers ask questions and get answers grounded in your reference.

  • Your domain

    Publish on a custom domain, subdomain or sub-path, with your logo, colours and fonts.

  • No lock-in

    Export your docs back to OpenAPI 3 at any time.

  • Copy prompt on every page

    Your users hand your API to their agent in one click, with one-click MCP connect for Cursor, VS Code and Claude.

One source, every format

Write it once. Every reader gets its format.

  • for people

    Docs site

    Searchable reference and guides with try-it and code samples.

    docs.acme.com/messages/send
  • for models

    llms.txt + markdown

    Every page has a .md twin; the site has llms.txt and llms-full.txt.

    GET docs.acme.com/llms.txt
  • for agents

    MCP server

    Hosted, on your domain, with search, contract and call tools.

    claude mcp add acme https://mcp.acme.com
  • for terminals

    CLI

    Every endpoint becomes a command.

    npx docstar-cli acme messages send
  • for tools

    OpenAPI

    A current OpenAPI file for SDK generators and gateways.

    GET docs.acme.com/openapi.json

Stays true

Docs that keep up with your API.

  • Never drifts

    DocStar watches your repo and drafts doc fixes when routes, params or responses change.

    • GitHub app
    • GitHub Actions sync
  • See who reads it

    People and agents, split by channel, with the questions they ask and the answers they couldn't find.

    • Docs, MCP, CLI, llms.txt

FAQ

API docs questions.

Do I need an OpenAPI file?

No. Your agent can write the docs from your code. If you have OpenAPI, Swagger or Postman, import it instead.

Can I see a live example?

Yes. MSG91's API docs at docs.msg91.com run on DocStar, including llms.txt and module.json for agents.

Can I keep guides next to the reference?

Yes. Guides, changelogs and endpoints live in the same project and share navigation and search.

Take the first step. Let your agent write your API docs.

One prompt. Your docs, MCP server and CLI, live.

Start free
API documentation for people and agents | DocStar