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 render.com

Full AI Authority Report (81/100) →
✓ Accept: text/markdown Active ✓ Vary: Accept Cache Header Set ✓ Content-Signal Policy (robots.txt) ✓ /llms.txt Fallback Active
Fetch Mode HTTP Header Sent Payload Size AI Tokens Token Savings
Standard Browser HTML Accept: text/html 748.4 KB 191,589 Baseline
Markdown for Agents Accept: text/markdown 5.2 KB 1,336 -99.3%
Static /llms.txt Summary GET /llms.txt 52.1 KB 13,332 -93%
✓ Active Content-Signal Policy (robots.txt): ai-train=yes, search=yes, ai-input=yes (Search: yes · AI RAG Input: yes · Model Training: yes)
Live Preview of Accept: text/markdown Response from render.com
# Render

Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web.

Source: https://render.com

# Your fastest path to production
for

Use cases: any workload, apps & agents, workflows, APIs & web apps, data pipelines, HIPAA apps

Intuitive infrastructure to scale any app or agent from your first user to your billionth.


- [Start for free](https://dashboard.rende

1-Click Content-Signal & Markdown Negotiation Config Builder

Cloudflare · Apache .htaccess · Nginx

Frequently Asked Questions

Technical Reference

What 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.