API delivery platform
Ship docs, SDKs, and agent context from one OpenAPI contract.
Build a hosted developer portal and strictly verified TypeScript, Python, and Go SDK artifacts from one canonical API graph. Publish consistent samples and llms.txt while the customer-facing MCP generation path remains held.
Hosted portals · TypeScript, Python, and Go SDKs · llms.txt · reproducible releases
contract.openapi.yaml
operationId: createPayment
method: POST
path: /payments
schema: PaymentRequestcompiled outputs
- portal API reference + sample
- sdk.ts verified client method
- sdk.py/go verified artifacts
- agent llms.txt + explicit MCP boundary
The mechanism
Stop maintaining each developer surface as a separate product.
Doctorine compiles once, then carries the same operation identities through the portal and generated artifacts. This example uses the tracked provenance from Doctorine's own TypeScript SDK dogfood build.
Download the complete SDK provenance receipt-
One canonical API graph
Import OpenAPI from a file or URL. Doctorine validates and compiles it once, then each supported downstream surface reads the same operation identities and schemas.
-
Verified developer artifacts
Generate TypeScript, Python, and Go artifacts with strict language-toolchain checks. Failures stay visible instead of becoming broken packages downstream.
-
Reproducible releases
Content-addressed snapshots make previews repeatable and activation reversible. When inputs do not change, generated bytes and their hashes do not change.
The platform
Three surfaces, one release model.
-
Developer portals
Publish guides and an OpenAPI reference as one hosted portal, with immutable releases and private-byte gating when access must be controlled.
Explore developer portals -
SDK generation
Produce TypeScript, Python, and Go SDK artifacts from the same graph, then inspect strict verification results and provenance hashes.
Explore sdk generation -
Agent-ready APIs
Publish llms.txt for entitled public portals and plan executable MCP tools against the same operation model without claiming the held generation path is live.
Explore agent-ready apis
Contract to release
A reviewable path, not a chain of hidden generators.
-
Import the contract
Upload an OpenAPI file or provide a URL. Validation reports the exact path, rule, and severity when the contract needs work.
-
Compile one graph
References resolve into a canonical model with stable operation identities, so docs and generated clients agree on what the API is.
-
Inspect related outputs
Review the hosted portal and SDK build candidates alongside agent-readable context before activating or distributing them.
-
Activate a snapshot
Publishing moves a pointer to an immutable release. Rollback moves it back; it does not rebuild history under a familiar URL.
Who it serves
For every team that serves developers, not only “API companies.”
Customer, partner, and internal APIs have different access and onboarding needs. They still benefit from a shared contract, consistent examples, verified clients, and releases that can be explained.
-
Customer APIs
Give external developers one reliable place to understand, test, and integrate with the API.
Plan delivery for customer APIs -
Partner APIs
Keep controlled integration guidance and generated client artifacts aligned for named partners.
Plan delivery for partner APIs -
Internal APIs
Bring public-quality reference, SDK, and change-safety practices to the interfaces your own teams consume.
Plan delivery for internal APIs
Available now
Specific claims, visible boundaries.
Doctorine is OpenAPI-first. It does not pretend every API uses OpenAPI, and it does not market roadmap controls as shipped enterprise features.
Read the trust posture-
OpenAPI ingestion
Import from a file or URL into one validation and compile pipeline.
-
Custom domains (assisted beta)
Use Cloudflare-managed TLS with assisted onboarding while stranger-grade self-serve DNS setup remains unverified.
-
Private portals
Gate private portal bytes at the edge before protected content is served.
-
Try-It explorer (beta)
Run calls through the hardened proxy only for explicitly allowlisted API hosts; the per-tenant production flow is not complete.
-
Agent-readable context
Publish llms.txt on eligible public portals; customer-accessible MCP generation remains held.
-
Scoped EU posture
EU data-at-rest for the core data plane, with declared non-EU processor carve-outs disclosed.
Bring the contract. Inspect every output.
Import an OpenAPI spec, review the generated surfaces and diagnostics, and decide from real artifacts instead of a feature checklist.