Field
Parameter rows for an API or SDK reference.
<Field value="projectId" type="string" required> The project to publish. </Field> <Field value="draft" type="boolean"> Keep the page out of navigation. </Field>
By use case
By team
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.
Point Doccupine at your code and get a structured reference site back, with no template wrangling and no infrastructure.
Doccupine reads your codebase: the routes, handlers, types, and the public surface your SDK exposes.
Endpoints, parameters, and request and response examples, structured into pages so you start from a real draft, not a blank one.
Managed hosting on your own custom domain, git-backed, with no build pipeline or infrastructure to run.
Docs live beside the code they describe, so a shipped change is never a stale page waiting to be caught.
The generated reference is a starting point you own. Edit it in a real editor, with git and MDX behind every change.
Draft or rewrite a block from a prompt right at your cursor, without leaving the page you are on.
Every change is a commit you can trace, diff, and roll back. Your docs carry the same history as your code.
Fields, badges, callouts, tabs, and code blocks out of the box, so a reference page reads the way an API deserves.
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.
Parameter rows for an API or SDK reference.
<Field value="projectId" type="string" required> The project to publish. </Field> <Field value="draft" type="boolean"> Keep the page out of navigation. </Field>
Highlighted, titled, one click to copy.
<Code
title="lib/slug.ts"
language="typescript"
code={`export function slugify(title: string) {
return title.trim().replace(" ", "-");
}`}
/>Statuses and versions, inline with prose.
<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>
One instruction, told per platform.
<Tabs>
<TabContent title="macOS" icon="Apple">
brew install doccupine
</TabContent>
<TabContent title="Linux" icon="Terminal">
npx doccupine
</TabContent>
</Tabs>Five tones for what a reader must not miss.
<Callout type="info"> Every page is plain Markdown or MDX. </Callout> <Callout type="warning"> Renaming a page changes its URL. </Callout>
A reference is only as useful as it is reachable. Every Doccupine site is built to be read by people and machines alike.
Every site ships an MCP server, so Claude, Cursor, and your own agents query your reference directly with citations.
Explore AI-ready docsHow Doccupine keeps every page in sync with the code it documents, automatically, as you ship.
See self-updating docsImport a GitHub repo and watch your API and SDK reference take shape, source-linked from day one. Free for 30 days, no credit card.