Reference docs that never drift from your code.
Generate your API and SDK reference straight from the repo, link every page to the source it documents, and let Doccupine flag or rewrite the docs the moment an endpoint changes.
Git-backed. Deploys to your own domain.
From repo to reference.
Point Doccupine at your code and get a structured reference site back, with no template wrangling and no infrastructure.
Import your repo.
Doccupine reads your codebase: the routes, handlers, types, and the public surface your SDK exposes.
AI drafts the reference.
Endpoints, parameters, and request and response examples, structured into pages so you start from a real draft, not a blank one.
Deploy to your domain.
Managed hosting on your own custom domain, git-backed, with no build pipeline or infrastructure to run.
Your reference stays true to your code.
Docs live beside the code they describe, so a shipped change is never a stale page waiting to be caught.
Source-linked, drift-detected.
- Pinned to the source.Every reference page records the exact file and commit it was generated from.
- Flagged when it changes.When that source changes, the page is flagged and rewritten to match the new behavior.
- Review or auto-publish.Stage each update for review or publish it straight to production, decided per page.
- Your edits are protected.A page you have touched by hand always routes to review, so the agent never overwrites your wording.
// commit a1b9f4c Add role endpoints- router.get("/users/:id", getUser);+ router.get("/users/:id", getUserV2);+ router.post("/users/:id/roles", assignRole);
Write and refine in place.
The generated reference is a starting point you own. Edit it in a real editor, with git and MDX behind every change.
AI compose in the editor.
Draft or rewrite a block from a prompt right at your cursor, without leaving the page you are on.
Version history from git.
Every change is a commit you can trace, diff, and roll back. Your docs carry the same history as your code.
MDX components.
Callouts, tabs, and code groups out of the box, so a reference page reads the way an API deserves.
Your reference, answerable over MCP.
A reference is only as useful as it is reachable. Every Doccupine site is built to be read by people and machines alike.
Make your API answerable to AI
Every site ships an MCP server, so Claude, Cursor, and your own agents query your reference directly with citations.
Explore AI-ready docsSee self-updating docs
How Doccupine keeps every page in sync with the code it documents, automatically, as you ship.
See self-updating docsShip reference docs that keep up.
Import a GitHub repo and watch your API and SDK reference take shape, source-linked from day one. Free for 30 days, no credit card.