agenticweb.md

What is agenticweb.md?

A Markdown file at your website root containing a strategic overview of your business: who you are, what you offer, how you differ, which agentic capabilities your site supports, and a recommended reading order pointing agents to the rest of the package. Where llms.txt is a concise index, agenticweb.md is the narrative, the file with room to explain.

Full transparency on authority: this is our own convention. We name it, design its structure, and own its evolution, and we label it that way in your package.

Why AI agents need it

The other files answer structural questions: what pages exist, what's permitted, what's structured. None of them answers "what is this business really about, and what can agents do here?" agenticweb.md fills that gap, and also serves as the declared home for agentic capabilities that have no static-file standard of their own, for example, an NLWeb deployment or a service endpoint an agent should know about.

The business value for you

AI systems get a more complete brand narrative than they can assemble from page titles alone, your positioning and differentiators in your own words, in a format agents actually ingest. Ramp's production experiment is the supporting evidence for the format choice: across roughly 50 marketing pages, Markdown was the only tested format that reliably surfaced in LLM responses.

Source: Ramp Builders, Marketing to AI agents

How it came to be

As we built packages, a gap kept appearing: standards cover indexes (llms.txt), permissions, and structured data, but no static file carries the business story or declares capabilities that lack their own well-known path. agenticweb.md is our answer, a deliberate composite, informed by the same agent-readable-Markdown evidence that anchors the rest of the package.

Adoption

As our own convention, adoption is by AgentReadyWebsite customers. Industry-wide adoption is not something we claim for it. If a published standard emerges that covers this ground, our quarterly authority review is designed to catch it and align.

The technical reality

The hard part isn't Markdown syntax, it's distillation. The file has to capture your actual differentiators from your real site content, describe every relevant capability accurately, cross-reference the other package files coherently, and stay current as your business evolves. We analyze your public pages to extract your business language, the generator structures it, and the managed subscription refreshes it monthly.

What happens if you skip it

Agents get your structure without your story: they can list your pages but not explain why a customer should choose you. Any capabilities without their own standard file simply go undeclared.