Source aligned
The specification remains the technical source for endpoints and schemas.
Agent-run API documentation
API documentation, built and kept current for you.
Hand SaturnDocs the API sources you already have. AI agents turn them into a usable quickstart, task guides, and an interactive reference, then maintain the whole set as the API changes.
The direct answer
What is agent-run API documentation?
Agent-run API documentation gives AI agents the work of turning an API’s technical sources into the material developers need to integrate: a quickstart, authentication guidance, task-based guides, request and response examples, and a complete reference. SaturnDocs agents write that material, publish the site, and keep the documentation aligned with the API.
A schema can describe endpoints and fields, but developers also need order, context, prerequisites, errors, and examples. SaturnDocs agents cover both layers so the reference and explanatory guides work together.
The reference
Your OpenAPI specification becomes an interactive reference.
SaturnDocs generates the API reference from your OpenAPI specification, organizes endpoints for the reader, and presents parameters, schemas, examples, responses, and authentication details in a consistent interface. When supported, readers can build and try requests directly from the reference.
Ready to explore
Readers can move from an operation to its parameters, examples, and responses.
Part of one site
The reference sits beside the quickstart, guides, search, and cited assistant.
The explanation
A reference answers what exists. Guides explain how to use it.
SaturnDocs writes the material an API specification cannot provide by itself: how to get a credential, make the first successful request, complete common workflows, handle failures, and choose between related operations. Those pages link directly to the relevant reference entries.
Readers can search the whole site or ask the documentation assistant. Its answers come from the published pages and include citations, so a short response always leads back to the complete instructions.
The ongoing work
Who maintains the API documentation after launch?
SaturnDocs agents maintain it. When an endpoint changes, a field is added, or an authentication flow moves, they revise the affected reference and guides. Your team can flag a problem at any time, and the correction becomes part of the same documentation source used by search, the assistant, llms.txt, and the MCP server.
Standard and Enterprise plans support API documentation programs of different sizes and complexity. The source remains exportable plain files.
API documentation questions
Frequently asked questions.
Do we need an OpenAPI specification?
An OpenAPI specification is the best source for an interactive API reference, but it is not the only way to start. Send the repository, existing reference material, request examples, or a walkthrough. We will tell you what is missing and build from the sources that exist.
Does the API reference let developers try requests?
Yes. When the API and its authentication model support it, the reference includes an interactive playground so a reader can inspect parameters, build a request, and see the expected response without leaving the docs.
Who keeps the API documentation current?
SaturnDocs agents do. They follow releases and changelogs, update guides and reference material when the API changes, and correct anything your team flags. Ongoing maintenance is included in every plan.
Do we own the API documentation?
Yes. The source lives in plain files that your team can read, edit, and export. The documentation SaturnDocs produces belongs to you.