Markdown to agents, HTML to humans

Delivering Markdown to Agents, HTML to Humans

This demo project shows how to serve different formats of the same documentation depending on the client. AI agents benefit from receiving lightweight Markdown instead of full HTML, while browsers still get standard HTML for human readers.

By serving Markdown directly, we cut down token usage for AI agents, making it more efficient for them to parse and process documentation.

Demo

Compare

1
 curl -H "Accept: text/markdown" https://markdown-to-agents.vercel.app/docs/getting-started

and

1
 curl -H "Accept: text/html" https://markdown-to-agents.vercel.app/docs/getting-started

How it works

The rewrite in next.config.ts directs traffic asking for text/markdown to a route that returns markdown.

1
const nextConfig: NextConfig = {
2
  rewrites: async () => {
3
    return {
4
      beforeFiles: [
5
        {
6
          source: "/docs/:slug",
7
          destination: "/markdown/:slug",
8
          has: [
9
            {
10
              type: "header",
11
              key: "accept",
12
              value: "(.*)text/markdown(.*)",
13
            },
14
          ],
15
        },
16
      ],
17
    };
18
  },
19
};