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

Full AI Authority Report (78/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 1,113.4 KB 285,023 Baseline
Markdown for Agents Accept: text/markdown 5.3 KB 1,370 -99.5%
Static /llms.txt Summary GET /llms.txt 5.8 KB 1,476 -99.5%
✓ Active Content-Signal Policy (robots.txt): search=yes, ai-input=yes, ai-train=yes (Search: yes · AI RAG Input: yes · Model Training: yes)
Live Preview of Accept: text/markdown Response from clerk.com
# Clerk — Everything you need for authentication

> More than APIs. The complete user layer for modern apps.

Add Clerk with an agent: `Add Clerk auth to my app: clerk.com/SKILL.md`

[Start building for free](https://clerk.com/docs/quickstart)

## Products

Each product ships with prebuilt UI components and the APIs behind them.

- [User Authentication](https://clerk.com/user-authentication): sign-up and sign-in, `<UserButton />`, `<UserProfile /

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.