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 turso.tech
Full AI Authority Report (76/100) →| Fetch Mode | HTTP Header Sent | Payload Size | AI Tokens | Token Savings |
|---|---|---|---|---|
| Standard Browser HTML | Accept: text/html |
150.4 KB | 38,501 | Baseline |
| Markdown for Agents | Accept: text/markdown |
1.6 KB | 420 | -98.9% |
| Static /llms.txt Summary | GET /llms.txt |
11.5 KB | 2,952 | -92.3% |
Accept: text/markdown Response from turso.tech# Turso: Millions of Databases. One Architecture. Built on SQLite. Lightweight enough to multiply, fast enough to run anywhere. Spin a database for every user, agent, and tenant. Turso is a ground-up rewrite of SQLite with concurrent writes (MVCC), async I/O, and built-in cloud sync. It runs embedded in your application, as a remote cloud database, or both. Turso is a drop-in replacement for SQLite: your existing SQL, schema, and queries work u
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.