A gear or action icon, representing the shift from descriptive to action-oriented site structure

What happens when an AI system can stop reading your site and start doing things on it?

The last post covered llms.txt, a file that tells an AI system what your site is about. There’s another newer convention developing aimed at action instead of description. Nobody has agreed on a name for it yet. Wix calls their version an agentic llms.txt. A separate emerging convention called AGENTS.md does something similar, it lists: the tools an agent can call, the endpoints, the auth requirements, and the rate limits. Another proposal, agents.txt, layers API declarations and MCP server details on top of the same base spec. These are different names for documents with essentially the same goal: to point agents not just at what your site says, but at what it can do.

A descriptive file, llms.txt, is like a table of contents while an action-oriented file would read more like an instruction manual (ie. here’s what an agent can act on, here’s how).

Mastercard already does this with their developer docs, pointing agents straight to the right API endpoint instead of leaving them to guess. Google’s Agent Development Kit does the same for their own coding tools. Both are current and live examples.

For a YMCA, the potential agentic actions could include: find nearby branches, compare membership options, check a class schedule, request counseling information, register for a program, find volunteer opportunities. Right now, a parent walks through those steps themselves, page by page, form by form. Adding an action-oriented layer is what eventually lets an assistant do the finding and the comparing and lead a person straight to the last step: confirming.

The true opportunity in AI is not replacing the person. It is in reducing the friction between “I want this” and “I got this.”

It will happen gradually and purposefully, the same as everything else we’ve talked about: accessible pages, clean structure, sitemaps, schema, and an honest llms.txt. Agents can only act on what they can already read and trust. All the boring, unglamorous groundwork turns out to be the actual prerequisite for the exciting part.

Search engines helped people find a page. What comes next is a system that can complete the task the page was made for.

Post 6, the last in this series. Post 1 introduced AI agents. Post 2 separated ranking, citation, and usability. Post 3 covered UX fundamentals. Post 4 covered sitemaps and schema. Post 5 covered llms.txt. Put together, that’s what “agentic readiness” actually means for a website right now: not a single file or feature, but the whole chain from readable to actionable.