Docs for agents, from the other founder

Why this conversation

What happens to documentation when most of its readers are machines? Sean Knight, who co-founded SaturnDocs with Alec Reynolds, came to AGNTCon + MCPCon North America in San Jose with an answer and with evidence: before the conference, his team had checked the docs of every vendor there. The host recorded with him on Thursday 22 October 2026, in the last conversation of the day. The rest of that day is in AGNTCon + MCPCon North America 2026: day one.

Readers that are not people

SaturnDocs is built on one premise: AI agents are on their way to becoming the main readers of developer and product docs. Sean’s snarkier way of saying it is that the people who will mostly read your docs will not be people at all. The web is becoming more agent than ever: at Cloudflare Connect, both of them had heard plenty about the statistic that agents have overtaken humans in how much they use the internet.

Asked what comes next, Sean turned the question back on the host, who talks to many founders. The host’s answer was two words he kept hearing at this conference: composability, one tool stacked on another, and accountability, being sure that the answers you get are correct. Sean applied both to docs. They have to be up to date, current and checked against the product, and AI agents have to be able to find and read them easily.

An audit of every vendor

Nearly every company there, Sean notes, has AI in its product, some of it built for agents specifically. Yet when SaturnDocs audited the docs of every single vendor before the event, the result was surprising: “A lot of them still don’t have things that AI would need to be able to easily consume those docs.” He named Markdown mirrors and llms.txt, and WebMCP, which he describes as a new standard for the web rather than a docs standard. Most companies’ docs have no WebMCP at all. Where a few do, it is only because someone on the team got very excited about it and worked out the implementation on their own time. The docs platforms do not offer it out of the box.

From migration to a Slack thread

The host asked where to begin for a team whose docs already sit in a wiki or a git repository. Sean’s answer: get in touch, because SaturnDocs handles migrations, with an agent built for moving docs from other platforms and tools. Before the customer commits or pays anything, it builds a complete version of their docs on SaturnDocs, so they can see it, test it with their own agents and review the results first. When the host praised that, Sean played it down: the agent does the work.

For keeping docs current there is a Slack tool. Suppose the product team has just shipped a feature and is talking about it in a channel. Someone tags SaturnDocs, asks it to read the thread and draft a new page for the feature, and it writes the draft in the voice the company’s docs already use. Review agents then go over the draft.

Will that be 100% accurate? Nothing is, Sean answers. There is an approval process, and each team chooses how much approval it wants. Docs kept by an engineer or anyone else are not 100% accurate either, and in his view docs maintained by agents still often beat the human alternative on accuracy.

One of his best examples comes from the question he asked everyone he talked to about docs here: which team manages them? He heard engineering, product, marketing, DevRel, and no one at all. In his words, “there’s rarely a person that just owns it.” There is often a technical writer, but without much authority over what goes in.

Getting started, and why Saturn

To get started, go to saturndocs.com and use the contact form. For now SaturnDocs onboards customers one at a time, to be sure each has a good experience, and follows them very closely. That cannot scale and will end, but the lessons about what works in the product and what does not are worth too much to miss.

As for the name: Sean trained as an astrophysicist and worked at NASA, and whenever he starts a company his first instinct is to give it a space theme. “Space is cool is really what it comes down to.”

When it comes out

The episode is edited and in the release order. Like every episode it goes out on YouTube first, then on Apple Podcasts, Spotify and Amazon Music.