Free “Markdown for Agents” (Accept: text/markdown) & Content-Signal Checker
Test in 1 click whether your website or Cloudflare edge serves clean Markdown when AI agents send Accept: text/markdown, measure exact token savings vs. raw HTML, and generate Content-Signal policy headers.
Live HTTP Content Negotiation Result for stripe.com
Full AI Authority Report (77/100) →| Fetch Mode | HTTP Header Sent | Payload Size | AI Tokens | Token Savings |
|---|---|---|---|---|
| Standard Browser HTML | Accept: text/html |
673.2 KB | 172,347 | Baseline |
| Markdown for Agents | Accept: text/markdown |
Server returned standard HTML instead of text/markdown |
||
| Static /llms.txt Summary | GET /llms.txt |
68.2 KB | 17,454 | -89.9% |
1-Click Content-Signal & Markdown Negotiation Config Builder
Cloudflare · Apache .htaccess · Nginx
Frequently Asked Questions
Technical ReferenceWhat is HTTP Accept: text/markdown ("Markdown for Agents")?
Markdown for Agents uses standard HTTP content negotiation: when an AI coding agent or crawler requests a URL with the header Accept: text/markdown, an edge network (such as Cloudflare) or origin server returns clean Markdown instead of bloated HTML—typically cutting token payloads by 80% to 99%.
What does the Content-Signal HTTP header control?
Content-Signal lets publishers declare machine-readable AI permissions across three directives: search (search result indexing), ai-input (real-time RAG/answer grounding), and ai-train (foundation model pre-training)—for example: Content-Signal: search=yes, ai-input=yes, ai-train=no.