Serve Markdown to AI Agents with Accept Headers

A new tool from an unnamed developer promotes serving Markdown versions of web pages to AI agents via HTTP content negotiation, using the `Accept: text/markdown` header to reduce token usage, improve retrieval signal-to-noise, and lower latency. The approach involves setting the `Vary: Accept` header, rejecting unsupported types with a 406 status, and honoring `q`-values, with a service that tests URLs from the edge to verify origin responses.

Serve Markdown to AI agents with content negotiation Accept: text/markdown Your site already has the content. Serving a Markdown variant lets agent AI clients skip nav/scripts/layout markup and read the content directly. - 01 — Tokens A fraction of the bytes. Markdown drops nav, styles, scripts, and layout wrappers. Agents spend context on your prose, not your DOM. - 02 — Retrieval Higher signal-to-noise. No ads, related-content rails, or modal overlays muddying the text a RAG pipeline has to embed. - 03 — Latency Faster first token. Less to fetch, less to parse, less to stuff into the context window before the model starts thinking. How AI-ready is your URL? - Serves Markdown for Accept: text/markdown - Sets Vary: Accept - Rejects unsupported types with 406 - Honors q -values Hit a URL with Accept: text/markdown . We make the request from our edge. See what the origin actually returns.