Mescio

Mescio for Agents makes your WordPress site AI-ready by silently serving posts, pages and WooCommerce products as clean, structured Markdown to any AI agent or LLM pipeline that requests it — using the standard HTTP <code>Accept: text/markdown</code> content negotiation header.
Human visitors using a browser are completely unaffected. Mescio for Agents only activates when an AI agent or crawler explicitly asks for Markdown.
<h4>Why Markdown?</h4>
Feeding raw HTML to an AI is expensive and noisy. A heading like <code>## About Us</code> costs ~3 tokens in Markdown vs 12–15 tokens as HTML — before accounting for <code><div></code> wrappers, navigation bars and script tags that carry zero semantic value. This blog post you are reading takes 16,180 tokens in HTML and 3,150 tokens in Markdown. That is an 80% reduction.
Markdown has become the lingua franca for AI systems. Mescio for Agents lets your site speak it natively, at zero cost to your human visitors.
<h4>How it works</h4>
When an HTTP client sends a request with <code>Accept: text/markdown</code>, Mescio for Agents intercepts the WordPress request lifecycle before any template is rendered, converts the post content to clean Markdown, and returns it with the correct <code>Content-Type: text/markdown</code> header.
<pre><code>curl https://yoursite.com/your-post/ \
 -H "Accept: text/markdown"
</code></pre>
<h4>Features</h4>
<ul>
<li>Zero configuration — works out of the box on any singular post, page or custom post type</li>
<li><code>/llms.txt</code> endpoint — auto-generated index of all your content in the <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a> standard format, so AI agents can discover what’s on your site</li>
<li><code>/llms-full.txt</code> endpoint — full site content in a single Markdown file, ready for RAG pipelines</li>
<li>WooCommerce support — product pages include price, SKU, stock status, rating, attributes and gallery; products are grouped by category in <code>llms.txt</code></li>
<li>YAML front matter — every document includes structured metadata (title, description, URL, date, categories, tags, featured image)</li>
<li>Multilingual — detects language via WPML, Polylang, TranslatePress or WordPress locale; emits <code>Content-Language</code> and <code>Link: rel=alternate</code> headers</li>
<li>REST API endpoint — <code>/wp-json/mescio-for-agents/v1/markdown?id=<post_id></code> or <code>?url=<permalink></code></li>
<li>Page builder cleanup — aggressively strips Elementor, Divi, WPBakery and Beaver Builder layout noise</li>
<li>Token count header — <code>X-Markdown-Tokens</code> tells AI pipelines how large the document is before processing</li>
<li>Content Signals — emits <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code></li>
<li>Correct HTTP caching — <code>Vary: Accept</code> ensures CDNs cache HTML and Markdown versions separately</li>
</ul>
<h4>Response headers</h4>
<ul>
<li><code>Content-Type: text/markdown; charset=utf-8</code></li>
<li><code>Content-Language: it</code> (or detected language)</li>
<li><code>Vary: Accept</code></li>
<li><code>X-Markdown-Tokens: 725</code></li>
<li><code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code></li>
<li><code>Link: <url>; rel="alternate"; hreflang="en"</code> (when translations available)</li>
</ul>
<h4>Multilingual plugin support</h4>
<ul>
<li>WPML — reads language and available translations automatically</li>
<li>Polylang — reads language and links to translated post IDs</li>
<li>TranslatePress — reads <code>trp_language</code> post meta</li>
<li>Manual — configure primary language and additional languages in Settings → Mescio for Agents</li>
</ul>
<h4>REST API</h4>
<pre><code>GET /wp-json/mescio-for-agents/v1/markdown?id=42
GET /wp-json/mescio-for-agents/v1/markdown?url=https://yoursite.com/my-page/
</code></pre>
<h4>Developer hooks</h4>
Filter: <code>mescio_enabled_post_types</code> — add or remove post types dynamically.
Filter: <code>mescio_pre_convert_content</code> — modify the HTML before conversion to Markdown.
Filter: <code>mescio_post_convert_content</code> — modify the Markdown after conversion.
<h4>Privacy</h4>
This plugin does not collect, store or transmit any personal data. It does not set cookies. It does not make external HTTP requests.

Mescio for Agents

Mescio for Agents serves your WordPress content as clean Markdown to AI agents and GPT crawlers. Human visitors never notice a thing.

gregrandall

AI agents, LLMs, and crawlers have to wade through navigation bars, sidebars, ads, and comment forms to reach the content they want, and every element costs tokens. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Botkibble adds a Markdown endpoint to every published post and page.
Cloudflare offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge on Pro, Business, and Enterprise plans. Botkibble does the same thing (for free) at the origin, so it works on any host.
<a href="https://github.com/greg-randall/botkibble" rel="nofollow ugc">GitHub Repository</a>
Three ways to request Markdown:
<ul>
<li><code>.md</code> suffix: append <code>.md</code> to any post or page URL (e.g. <code>example.com/my-post.md</code>)</li>
<li>Query parameter: add <code>?format=markdown</code> to any post or page URL</li>
<li>Content negotiation: send <code>Accept: text/markdown</code> in the request header</li>
</ul>
What’s in every response:
<ul>
<li>Structured metadata header with title, date, categories, tags, word count, character count, and estimated token count (in YAML frontmatter format, readable by any AI agent)</li>
<li>Clean Markdown converted from fully-rendered post HTML (shortcodes run, filters applied)</li>
<li><code>Content-Type: text/markdown</code> and <code>Vary: Accept</code> response headers</li>
<li><code>Content-Signal</code> header for AI signal declaration — defaults to <code>ai-train=no, search=yes, ai-input=yes</code> — see <a href="https://contentsignals.org/" rel="nofollow ugc">contentsignals.org</a></li>
<li><code>X-Markdown-Tokens</code> header with estimated token count</li>
<li>Discovery via <code><link rel="alternate"></code> in the HTML head and <code>Link</code> HTTP header</li>
<li>Automatic cache invalidation when a post is updated or deleted</li>
</ul>
Performance:
Botkibble writes Markdown to disk on the first request, then serves it as a static file. A built-in Fast-Path serves cached files during WordPress’s <code>init</code> hook, before the main database query runs. No extra configuration needed.
Add a web server rewrite rule and Botkibble bypasses PHP entirely, serving <code>.md</code> files the same way a server would serve an image or CSS file:
 Method 
 Avg. response time
 Standard HTML 
 0.97s
 Markdown (cold, first request) 
 0.95s
 Markdown (cached, PHP Fast-Path) 
 0.87s
 Markdown (Nginx/Apache direct) 
 0.11s
Serving directly from disk is 88% faster than a full WordPress page load. See the Performance section below for Nginx and Apache configuration.
Security:
<ul>
<li>Drafts, private posts, and password-protected content return <code>403 Forbidden</code></li>
<li>Rate limits cache-miss regenerations (20/min by default) to mitigate DoS abuse</li>
<li><code>X-Robots-Tag: noindex</code> keeps Markdown versions out of search results</li>
<li><code>Link: rel="canonical"</code> points search engines back to the HTML version</li>
</ul>
Cache variants (optional):
You can persist alternate cached representations by adding <code>?botkibble_variant=slim</code> (or any other variant name). 
Variant caches are stored under:
<pre><code>/wp-content/uploads/botkibble/_v/<variant>/<slug>.md
</code></pre>
What it does NOT do:
<ul>
<li>Expose drafts, private posts, or password-protected content</li>
<li>Serve non-post/page content types by default</li>
<li>Require any configuration. Activate and it works.</li>
</ul>
<h3>Why Markdown?</h3>
HTML is expensive for AI systems to process. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Cloudflare now offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge via the <code>Accept: text/markdown</code> header, available on Pro, Business, and Enterprise plans.
This plugin does the same thing at the origin, so it works on any host. It also adds <code>.md</code> suffix URLs, <code>?format=markdown</code> query parameters, YAML frontmatter, static file caching, and server-level offloading.
If you use Cloudflare, both share the same <code>Accept: text/markdown</code> header, <code>Content-Signal</code> headers, and <code>X-Markdown-Tokens</code> response headers.
Cloudflare currently defaults to <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code> with no way to change it. Botkibble defaults to <code>ai-train=no</code> and lets you override the full signal per site via the <code>botkibble_content_signal</code> filter.
<h3>Performance & Static Offloading</h3>
This plugin supports static file offloading by writing Markdown content to <code>/wp-content/uploads/botkibble/</code>.
<h3>Nginx Configuration</h3>
To bypass PHP entirely and have Nginx serve the files (including variants) directly:
<pre><code># Variants
location ~* ^/(_v/[^/]+/.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}

# Default
location ~* ^/(.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}
</code></pre>
<h3>Apache (.htaccess)</h3>
Add this to your <code>.htaccess</code> before the WordPress rules:
<pre><code>RewriteEngine On
# Variants
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/_v/$1/$2.md -f
RewriteRule ^_v/([^/]+)/(.+)\.md$ /wp-content/uploads/botkibble/_v/$1/$2.md [L,T=text/markdown]

# Default
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/$1.md -f
RewriteRule ^(.*)\.md$ /wp-content/uploads/botkibble/$1.md [L,T=text/markdown]
</code></pre>
Even without these rules, the plugin uses a “Fast-Path” that serves cached files from PHP before the main database query is executed.
<h3>Credits</h3>
We thank Cristi Constantin (https://github.com/cristi-constantin) for contributing cache variants, URL and SEO improvements, and fixing important bugs.

Botkibble

Serves every published post and page as Markdown for AI agents and crawlers. No configuration, no API keys. Activate and it works.

Mescio for Agents vs Botkibble