# API documentation, built and kept current for you.

SaturnDocs uses AI agents to build and maintain API documentation, quickstarts, guides, and an interactive OpenAPI reference.

×

Agent-run API documentation

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.

Agent-run API documentation

## Turn technical sources into a complete API guide.

SaturnDocs agents turn your 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. They publish the site and keep every page aligned with the current API.

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.

API reference openapi.yaml

GET `/v1/matters` 200 OK

Query parameters

str

**status**open, closed, or archived

optional

int

**limit**1 to 100, defaults to 25

optional

Parameters, schemas, and responses come straight from the specification

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.

The ongoing work

## Agents maintain the 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](https://saturndocs.com/pricing/) support API documentation programs of different sizes and complexity. The source remains exportable plain files.

Maintenance queue 1 flagged

◆

**Release v3.2 shipped**POST /v1/matters gained a required field

!Reference / Create a matter

No longer matches the current API

`_−_{ "title": "string" }` `_+_{ "title": "string", "matterType": "string" }`

YC

Reference and guides revised together

Approve and publish

API documentation questions

## Frequently asked questions.

Ask us something else

### 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.

Start with what exists

## Send the specification, repository, or current API docs.

[Send us your docs](https://saturndocs.com/contact/?intent=docs)

Canonical URL: https://saturndocs.com/api-docs-by-ai-agents/