Specifications are incomplete explanations
A schema describes the interface but rarely teaches the first successful workflow.
API documentation
Reference generated from the contract. Guidance written for the task.
Bring OpenAPI reference, hand-written concepts, working examples, and change evidence into one published developer experience.
The operating problem
Publishing is one moment. Accuracy is continuous.
Breaking changes reach prose late
Authentication, errors, and examples can keep describing an operation after it moves.
Readers use many entry points
Search, direct URLs, agents, and copied examples must resolve to the same reviewed source.
The workflow
One source from draft through evidence.
Let the API contract drive reference without asking it to replace explanation.
OpenAPI reference
Create operation pages from OpenAPI 3.0 or 3.1 alongside authored documentation.
Impact detection
Connect high-confidence breaking changes to the pages that describe the operation.
Reusable examples
Keep snippets, variables, tabs, and code blocks consistent across guides and reference.
Agent-ready access
Serve semantic HTML, Markdown, llms.txt, API, and MCP from one permission model.
What changes