Serve Markdown to AI Agents with Accept Headers

Serve Markdown to AI agents pinch contented negotiation

Your tract already has the content. Serving a Markdown variant lets supplier AI clients skip nav/scripts/layout markup and publication the contented directly.

• 01 — Tokens

  A fraction of the bytes.

  Markdown drops nav, styles, scripts, and layout wrappers. Agents walk discourse connected your prose, not your DOM.

• 02 — Retrieval

  Higher signal-to-noise.

  No ads, related-content rails, aliases modal overlays muddying the matter a RAG pipeline has to embed.

• 03 — Latency

  Faster first token.

  Less to fetch, little to parse, little to worldly into the discourse model earlier the exemplary starts thinking.

How AI-ready is your URL?

1. Serves Markdown for Accept: text/markdown
2. Sets Vary: Accept
3. Rejects unsupported types pinch 406
4. Honors q-values

Hit a URL with
Accept: text/markdown.

We make the petition from our edge. See what the root really returns.

Where to next.

• Quick start The smallest moving setup Three steps. One server, 2 responses.
• Guides Fundamentals & correctness Vary, q-values, 406, caching, and the Cloudflare zero-config shortcut.
• Recipes Copy-paste configs Nginx, Caddy, WordPress, Discourse, Laravel, Rails, Cloudflare Workers, Next.js, Astro, Apache, SvelteKit, Nuxt/Nitro, Express, Go, Django.
• Status AI supplier support matrix Which AI agents nonstop Accept: text/markdown erstwhile their browse aliases fetch devices deed a URL.
• Reference Standards & sources RFC 9110, RFC 7763, the text/markdown media type, and adjacent specs.