API & SDK documentation

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 is auto-linked to the exact file and commit it was generated from. No manual mapping.
  • 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.

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.

Fields, badges, callouts, tabs, and code blocks out of the box, so a reference page reads the way an API deserves.

The reference toolkit, live.

These are the real components your pages are built from, fields to badges to code blocks, rendered right here with the MDX that produces them.

Field

Parameter rows for an API or SDK reference.

projectIdstringrequired
The project to publish.
draftboolean
Keep the page out of navigation.
MDX
<Field value="projectId" type="string" required>
  The project to publish.
</Field>

<Field value="draft" type="boolean">
  Keep the page out of navigation.
</Field>

Code

Highlighted, titled, one click to copy.

MDX
<Code
  title="lib/slug.ts"
  language="typescript"
  code={`export function slugify(title: string) {
  return title.trim().replace(" ", "-");
}`}
/>

Badge

Statuses and versions, inline with prose.

Stablev2.1.0BetaDeprecated
MDX
<Badge color="green" icon="circle-check">Stable</Badge>
<Badge color="blue" solid>v2.1.0</Badge>
<Badge color="orange" stroke>Beta</Badge>
<Badge color="red" shape="pill">Deprecated</Badge>

Tabs

One instruction, told per platform.

brew install doccupine
MDX
<Tabs>
  <TabContent title="macOS" icon="Apple">
    brew install doccupine
  </TabContent>
  <TabContent title="Linux" icon="Terminal">
    npx doccupine
  </TabContent>
</Tabs>

Callout

Five tones for what a reader must not miss.

Every page is plain Markdown or MDX.
Renaming a page changes its URL.
MDX
<Callout type="info">
  Every page is plain Markdown or MDX.
</Callout>

<Callout type="warning">
  Renaming a page changes its URL.
</Callout>

Ship reference docs that keep up with your code.

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.