Practical guides for shipping an API people can use.
Plan documentation, SDK, CLI, MCP, Agent Skill, and migration workflows with tested checklists, worked examples, and clear product limits.
Start with the decision in front of you.
Each guide gives you a method, the evidence to inspect, and the limits to plan around.
- 01Read the guide
API Delivery vs API Management: Where Each Fits in the API Lifecycle
API management governs runtime traffic and policy. API delivery turns a contract into docs, SDKs, examples, and agent tools. Learn where each belongs.
Standards-linked lifecycle boundaries and a claims-audited Doctorine capability map.
- 02Read the guide
Docs as Code: A Workflow That Prevents API Drift
Use this docs-as-code workflow to review prose, OpenAPI, examples, generated reference, and release evidence together without creating a second source of truth.
Includes a seven-stage workflow, pull-request checklist, ownership map, and failure-mode review.
- 03Read the guide
OpenAPI to MCP: Build Safe, Useful Agent Tools
A practical OpenAPI-to-MCP workflow for operation selection, tool schemas, descriptions, authorization, side effects, testing, and release verification.
Includes a worked operation mapping, release checklist, security boundaries, and verification matrix.
- 04Read the guide
API Documentation Examples: A Practical Evaluation
Evaluate API documentation examples with a first-call rubric covering orientation, authentication, requests, responses, errors, operations, and change safety.
Includes annotated patterns, an evidence-based scorecard, and a review exercise your team can reuse.
Find the guide for your question.
Move from the problem you are solving to the Doctorine product that supports it.
- 01Run the free benchmark
Can agents actually use our website?
Run Cloudflare’s independent benchmark, inspect every returned signal, and compare the result with Doctorine’s versioned publishing baseline.
- 02Explore Documentation
How should a documentation release work?
Connect guides, reference, examples, preview, review, access, and rollback without maintaining a second publishing system.
- 03Explore Verified SDKs
What makes a generated SDK trustworthy?
Inspect the TypeScript, Python, and Go verification plans, release identities, and artifact-withholding boundary.
- 04Explore the CLI
Can the platform fit terminal-first work?
Use human-readable commands or stable structured output to inspect projects, validate changes, and control releases.
- 05Explore MCP
Which MCP trust boundary do we need?
Separate public documentation reading, authenticated workspace change control, and a locally generated API MCP server.
- 06Explore Agent Skills
How does API knowledge travel with an agent?
Package SKILL.md, references, recipes, API material, and provenance into one installable Agent Skill.
- 07Explore the platform
How do these products stay aligned?
See how one release connects every interface while dashboard, CLI, and MCP provide deliberate control surfaces.
Tested, owned, and kept current.
Every guide names its maintainer, review scope, tested date, and refresh date.
- Every guide names a maintainer, review scope, and tested date.
- Unsupported protocols, authentication gaps, and manual work appear where they matter.
- Checklists, worked examples, and verification steps replace decorative summaries.
- Every method links to the product surface that puts it into practice.
See how the products work together.
Explore each product in depth, then choose the workflow that fits the API experience you are building.