Agents fetch web pages to answer questions, write code, and complete tasks. When an agent requests a page, it gets everything your browser gets, including navigation menus, stylesheets, JavaScript bundles, tracking scripts, and footer links, when all it needs is the structured text on the page. That extra markup confuses the agent, consumes its context window, and makes every request more expensive. What agents need is a way to request just the text content of a page, without the browser-specific markup. solves this. It's a standard HTTP mechanism where the client specifies its preferred format via the header, and the server returns the matching representation.

Many agents already send when fetching pages, and a server that supports content negotiation can return clean, structured text from the same URL that serves HTML to a browser.Content negotiationAcceptAccept: text/markdown We've updated many of our pages, including our blog and changelog, to support content negotiation. This post walks through how it works, how we implemented it in Next.js, and how to add markdown sitemaps so agents can discover your content. When an agent fetches a page, it includes an header with its…