What it is

Agents read a page more cheaply and more correctly as markdown than as HTML full of menus and scripts. A site can serve the same content in both forms.

An analogy

A large-print edition of the same book: same words, easier to read for the person who needs it.

At a glance

Owner
A convention, used by Cloudflare, Vercel and documentation platforms
Maturity
Emerging No formal specification. Two patterns are common: add .md to a page address, or answer an Accept: text/markdown request with markdown.
Where it lives
No official specification. It is a convention or a label.
Framework domain
Discover: Be found
What it serves
  • Make pages cheap and accurate for agents to read

Who should care

The roles this standard touches most. See all the roles on the personas page.

  • Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
  • Marketing and brand. Own the story agents tell: accurate facts, positioning, reputation and presence where agents look.

Framework personas →

How to adopt it

  1. 1

    Pick one pattern: a .md address or content negotiation with the Accept header.

  2. 2

    Generate the markdown from the same source as the page so the two never disagree.

  3. 3

    Link to it from llms.txt.

The Institute’s view

Adopt with care

Worth doing on documentation and key pages. Without a spec, tools differ. Keep the markdown identical in substance to the page, or you create two versions of the truth.

Standards change fast. Last reviewed November 2026.

← Back to the Standards Map