Skip to main content
Doctorine

Ship docs, SDKs, CLI, and skills.md from your OpenAPI spec.

Import the spec. Doctorine generates a hosted portal, TypeScript, Python, and Go SDKs, a CLI, MCP, and Agent Skills. It checks each one. You publish only what passed.

Become a Design PartnerSee the outputs

Start with a file or a URL.

The API moved. The docs and SDKs usually did not.

Docs wait. Examples get copied into Slack. SDKs regenerate in another tool. Agents keep reading last week's version.

Doctorine generates all of them from the same spec, checks them, and publishes only what passed.

  • Before

    Docs, SDKs, and agent tools each live in a different tool, on a different version.

  • When the API changes

    Someone updates pages, packages, and snippets by hand.

  • After you ship

    You cannot say which version developers are using.

Import the spec. Check the outputs. Publish what passed.

Doctorine compiles the OpenAPI file and generates each output from that version.

You preview the candidate. You publish the portal and the artifacts you picked. If something is wrong, you roll back.

  1. Import

    Bring OpenAPI from a file or URL.

  2. Review

    See what docs, methods, examples, and packages would change.

  3. Verify

    Run the checks each output needs. A failed SDK stays failed.

  4. Publish

    Put the portal live and deliver the artifacts you selected.

  5. Roll back

    Return to the previous publish without rebuilding history.

Release rls_0138
Verified
Approved sourcePayments API · revision 184Content and API model locked for this release
  1. DocumentationPublished
  2. Verified SDKs3 languages
  3. CLI contextReady
  4. MCPDiscoverable
  5. Agent SkillPackaged

What the spec produces.

  1. Documentation

    Hosted guides, reference, versions, search, and private access.

    Explore Documentation

  2. Verified SDKs

    TypeScript, Python, and Go clients. They ship only after language checks pass.

    Explore Verified SDKs

  3. CLI

    Generate, compare, and publish from your machine or CI.

    Explore CLI

  4. MCP

    Agents read the published docs, or make scoped workspace changes, through separate permissions.

    Explore MCP

  5. Agent Skills

    The operating notes a schema cannot hold, in open files you can inspect.

    Explore Agent Skills
Explore the platform

People and agents should see the same API version.

The hosted docs, page Markdown, llms.txt, MCP, and Agent Skills all come from the version you published.

Same spec. Same version. Different format.

Agents get their own format and permissions. They still read the version you published, not a separate copy.

You can see what was generated, what passed, and what went live.

Each publish records the spec, the generator, the checks, and the output hashes.

A failed SDK target stays failed. A live portal can roll back. A migration report shows what did not map.

  • Verified SDKs

    TypeScript, Python, and Go must pass their language checks before you can deliver them.

  • Rollback

    Preview is reproducible. Switching the live portal back does not rewrite history.

  • Receipts

    Each receipt names the accepted API model, configuration, generator, and output hashes.

Inspect a real SDK receipt
Generator
@doctorine/sdk-codegen
Version
0.3.4
Language
TypeScript
Bundle
e1071c55ff27…
SDK
48fe7201a2be…

See what a move from ReadMe, Mintlify, Fern, Speakeasy, or Stainless would keep.

Run a scored assessment on a supported export. The report says what maps, what degrades, what needs a person, and what cannot come across, before you switch.

Run a migration assessmentSee supported migration inputs

For APIs that customers, partners, or internal teams have to use.

  • Public APIs

    Help prospects and customers get from the docs to a working integration.

    See the workflow

  • Partner APIs

    Give named partners controlled access without forking the API facts.

    See the workflow

  • Internal APIs

    Replace tribal knowledge with current docs, clients, and publish history.

    See the workflow

Not your API gateway.

Doctorine does not route traffic, issue tokens, or replace Git.

Import a spec. Generate docs, SDKs, and agent tools. Publish what passed. Roll back if you need to.

Import a spec and look at the outputs.

Use a file or a URL. Check the portal and the SDKs. Decide if the workflow fits.

Become a Design PartnerTalk through a migration