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

Full AI Authority Report (87/100) →
✓ Accept: text/markdown Active ✓ Vary: Accept Cache Header Set ✓ Content-Signal Policy (HTTP Header) ✓ /llms.txt Fallback Active
Fetch Mode HTTP Header Sent Payload Size AI Tokens Token Savings
Standard Browser HTML Accept: text/html 1,303.2 KB 333,631 Baseline
Markdown for Agents Accept: text/markdown 2.9 KB 747 -99.8%
Static /llms.txt Summary GET /llms.txt 16.8 KB 4,294 -98.7%
✓ Active Content-Signal Policy (HTTP Header): 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 cloudflare.com
---
title: "Cloudflare - Global Serverless Platform"
description: "Deploy serverless code instantly across the globe with zero cold starts, infinite scalability, and integrated storage, AI, and network services."
url: "https://www.cloudflare.com"
---

# Cloudflare

> Deploy serverless code instantly across the globe with zero cold starts, infinite scalability, and integrated storage, AI, and network services.

## What is Cloudflare Workers?

Clou

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.