# How agent-first documentation works. The SaturnDocs process: turn existing product context into documentation that AI agents can find, cite, and follow, then keep every surface current. × Give SaturnDocs your product context. The agents turn it into documentation that AI agents can discover, cite, and follow, then keep every published surface current as your product evolves. [Send us your docs](https://saturndocs.com/contact/?intent=docs) [See the platform](https://saturndocs.com/platform/) From hand-over to maintenance ## What makes documentation agent-first? Agent-first documentation gives AI agents a direct path to understand what your product does, decide when to recommend it, and complete the customer’s task. SaturnDocs publishes the same product knowledge for people and agents, then keeps every surface current. [See the surfaces agents use](https://saturndocs.com/docs-for-ai-agents/) The hand-over ## Start with the docs you already have. An existing docs site, a repository, an OpenAPI spec, help-center articles, or internal notes. You do not clean anything up first; the agents take over what exists. Most teams spend about fifteen minutes here. The hand-over About 15 minutes git **github.com/yourcompany/api**Repository access received yml **openapi.yaml**API specification received zip **old-docs.zip**Previous docs site export received md **notes.md**Scattered internal notes received rec **walkthrough-call.m4a**One hour with your team received Nothing was cleaned up first. The build ## The agents read everything and draft your docs. The agents read the code, the spec, and every note, then structure it all into clear guides, a quickstart, and an interactive API reference, in your brand and on your domain. Your first draft is ready within 24 hours. saturndocs · build \>Build the docs for Your Company from the hand-over. ●Read _214 source files_ ●Parse _openapi.yaml · 61 endpoints_ ●Import _3 old pages · notes.md_ ●Write _quickstart · 18 guides · API reference_ Draft docs assembled in **your brand**, on **your domain**, with search and the AI assistant wired in. ↳ first draft ready in under 24 hours The review ## Follow one product change through the docs. See what the agents receive, what they change, and what you approve. 1. 1Product context 2. 2Documentation produced 3. 3Review 4. 4Published result ### The product change We just replaced API keys with scoped access tokens. Update the authentication docs, API quickstart, and migration guidance. Keep the old flow documented through September 30. **Maya** · Product engineering feat/scoped-access-tokens Prepare documentation The launch ## Your docs go live on your domain. Search, the interactive API reference, the cited assistant, llms.txt and Markdown for agents, reader authentication, analytics, and hosting with TLS are already wired in. You add one DNS record to put the docs on your domain; we send you the exact record, and then you send people the link. The launch Live docs  CNAME  yourcompany.saturndocs.com you add this tls **Hosting and TLS**handled on our side active srch **Search and AI assistant**wired in before launch ready llms **llms.txt and reader auth**agents and permissions covered ready get **docs.yourcompany.com**your domain, your brand 200 OK Then you send people the link. The loop ## From then on, the docs keep up. Ship a release and the agents draft the update; approve it from Slack, Claude, the command line, or the dashboard. Questions your readers repeat become new pages, and insights show what to fix next. The four steps above happen once; this upkeep is included in your plan. The loop Always on ◆ **Release v3.2 shipped**rate limit raised on the write API **Drafted fix ready**Guides / Rate limits Slack Claude Dashboard **“Which scope does a webhook subscription need?”**asked 34 times this week Draft answer ready ✓ **Published**last week’s fix is live for the next reader The four steps happen once. The loop keeps going. ## Frequently asked questions. Ask us something else ### How much of our time does it take? About fifteen minutes to hand things over, and however long you want to spend reviewing the draft. The one technical step on your side is adding a single DNS record so the docs live on your domain; we send you the exact record to add. ### What if we barely have any docs? Code and a conversation are enough. Products with no docs at all are some of our favorite starts, because there is nothing to untangle. ### Do we have to migrate anything? No. Send links to what exists and the agents handle the moving, restructuring, and rewriting. ### What happens after launch? SaturnDocs keeps the human and agent-facing documentation current. You can ask for an update from Claude, the command line, Slack, or the dashboard, and you can always edit the plain files yourself. Your docs are waiting ## Hand it over once. The agents keep up from there. Everything after the hand-over is a change you review and approve. [Send us your docs](https://saturndocs.com/contact/?intent=docs) Canonical URL: https://saturndocs.com/the-process/