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.
One accepted API release, expressed for every way developers and agents work.
Hosted guides, reference, versions, search, and private access.
Use a scoped service token in the Authorization header.
Authorization: Bearer dtn_live_••••TypeScript, Python, and Go clients. They ship only after language checks pass.
import { Payments } from '@acme/payments';
const client = new Payments({
apiKey: process.env.PAYMENTS_API_KEY
});
const charge = await client.charges.create({
amount: 2400,
currency: 'eur'
});48fe7201…Generate, compare, and publish from your machine or CI.
❯ doctorine compare
content 3 pages changed
api model 2 operations changed
sdk impact typescript · python · go
❯ doctorine publish --json
{"release":"rls_0138","status":"live"}
❯ doctorine status
portal live
sdk builds 3 verified
skill readyAgents read the published docs, or make scoped workspace changes, through separate permissions.
docs.searchFound “Authentication”readchanges.stage_pageUpdated token scopesallowedchanges.previewImmutable preview builtauditedThe operating notes a schema cannot hold, in open files you can inspect.
# Payments API
Creating charges, handling refunds, or verifying webhook signatures.
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.
Docs, SDKs, and agent tools each live in a different tool, on a different version.
Someone updates pages, packages, and snippets by hand.
You cannot say which version developers are using.
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.
Bring OpenAPI from a file or URL.
See what docs, methods, examples, and packages would change.
Run the checks each output needs. A failed SDK stays failed.
Put the portal live and deliver the artifacts you selected.
Return to the previous publish without rebuilding history.
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.
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.
TypeScript, Python, and Go must pass their language checks before you can deliver them.
Preview is reproducible. Switching the live portal back does not rewrite history.
Each receipt names the accepted API model, configuration, generator, and output hashes.
e1071c55ff27…48fe7201a2be…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.
Help prospects and customers get from the docs to a working integration.
See the workflowGive named partners controlled access without forking the API facts.
See the workflowReplace tribal knowledge with current docs, clients, and publish history.
See the workflowDoctorine 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.
Use a file or a URL. Check the portal and the SDKs. Decide if the workflow fits.