Markdown Negotiation Support

Serve Markdown to agent clients by detecting the Accept: text/markdown HTTP header in incoming requests and returning Markdown content instead of the default HTML response format.

Markdown content negotiation requires setting Content-Type to text/markdown, including Vary: Accept, and providing an x-markdown-tokens header with an estimated token count for LLM processing.

Content negotiation for LLM token estimation works by intercepting agent HTTP requests with Accept: text/markdown, returning Markdown formatted content, and attaching the x-markdown-tokens header with estimated token counts.

Markdown content negotiation keeps HTML as the default representation for browsers, only switching to Markdown output when an agent explicitly requests it via the Accept: text/markdown header.

You can use HTTP Accept headers to control output representation by sending Accept: text/markdown to receive Markdown content with token estimates, or omitting it to receive the default HTML response.