p.enthalabs

Serve Markdown to AI Agents with Accept Headers

Serve Markdown to AI agents with content negotiation

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?

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

Hit a URL with

`Accept: text/markdown`.

We make the request from our edge. See what the origin actually returns.

Where to next.

- Quick start The smallest working setup Three steps. One server, two 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.](https://acceptmarkdown.com/recipes)

- Status AI agent support matrix Which AI agents send `Accept: text/markdown` when their browse or fetch tools hit a URL.

- Reference Standards & sources RFC 9110, RFC 7763, the `text/markdown` media type, and adjacent specs.