SaturnDocs: docs that agents read and write

Sean Knight is co-founder of SaturnDocs, with Alec Reynolds. Luca Berton talked to him at AGNTCon + MCPCon North America 2026 in San Jose on 22 October 2026, in the last recording of the day. The day before, in San Francisco, Alec had explained documentation written for agents; this is the other founder’s turn.

The readers are not people

The premise behind SaturnDocs, Sean says, is that “AI agents are going to be the primary consumers of developer docs, of product docs.” The snarky version: “the people who will primarily be consuming your docs are not people.” Both he and Luca had heard at Cloudflare Connect that agents have passed humans in how much they use the internet.

Sean turned the next question round and asked Luca what the next big thing is. Luca’s answer was two words he kept hearing at this conference: composability and accountability. Sean took it to the docs: “Documentation should be up to date. It should be current. It should be verified against your product. But it also needs to be really findable and readable by AI agents.”

An audit of the floor

Before the conference, SaturnDocs audited the docs of every vendor at it. Almost every company there has AI in its product, many of them something built for agents, and still a lot of their docs lack what an agent needs to read them easily: a Markdown mirror, llms.txt, and WebMCP, a new standard for the web. Most have no WebMCP at all. The few that do have it “because someone on the team got really excited about it and spent time on their own figuring out how to implement it.” Docs platforms do not implement it out of the box.

A migration before you pay

Luca asked where to start for a team whose docs live in a wiki or a git repository. SaturnDocs does the migration, with an agent built to move docs from other platforms and tools. Before a customer pays anything, it builds a full version of their docs on the platform, so they can see it and test it with their own agents first. “Well, our agent does the work. It’s actually not that big of a deal.”

A docs page from a Slack thread

To keep the docs current, you tag SaturnDocs in a Slack thread, for example the one where the product team discussed a feature just released, and ask it to read the thread and draft a docs page. It writes in the voice the docs already use, and review agents check the draft.

Is it 100% accurate? “Well, nothing’s 100% accurate.” There is an approval process, as strict as the team wants. Docs that people maintain are not 100% accurate either, and agent-maintained docs, he says, are “still often more accurate than the human alternative.”

He asked everyone at the conference which team manages their docs. He heard engineering, product, marketing, DevRel, and no one: “docs don’t have a defined home.” There is often a technical writer, without much authority over what goes in.

How to start

The way in is the contact form at saturndocs.com. SaturnDocs onboards its customers one by one for now: “We are babysitting very closely.” It does not scale and will stop, but what the team learns about what works in the product “is too valuable to pass up.”

And the name? Sean is an astrophysicist by training and worked at NASA, and he wants every company he starts to have a space theme. “Space is cool is really what it comes down to.”

More

The episode with Sean Knight is being produced and goes out on YouTube first. Alec Reynolds’s conversation: SaturnDocs: documentation written for agents. Everyone the show has met there: SaturnDocs on Udienza. The day it was recorded: AGNTCon + MCPCon North America 2026: day one.