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


simple, plug and play, for any website; implemented on tens of sites and validated the setup with cloudflare's free isitagentready.com check for content, everything is in the green.


plug and play AI discoverability

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

kkarpieszuk

Kolibia Agent-Ready makes WordPress content available as Markdown so tools and agents do not have to scrape HTML. Behaviour follows common content negotiation patterns (similar in spirit to <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> on Cloudflare): clients that prefer Markdown can request it explicitly.
What is included today
<ul>
<li>Markdown responses for singular content — For each built-in public post type registered by WordPress core (<code>post</code>, <code>page</code>, <code>attachment</code> on a typical site), a single-item URL can return <code>Content-Type: text/markdown; charset=UTF-8</code> instead of the themed HTML page.</li>
<li>Markdown for the posts index — When the site front page shows latest posts (WordPress “Your homepage displays: Your latest posts”), the homepage and other blog-index URLs return Markdown listing the same posts as the main loop.</li>
<li>Static or WooCommerce shop front page — When a page is set as the front page (including a WooCommerce shop page where WordPress reports <code>is_singular</code> as false), that page’s content is still served as Markdown on <code>/</code> when clients negotiate <code>text/markdown</code>.</li>
<li>When Markdown is served
<ul>
<li>The request includes an <code>Accept</code> header that lists <code>text/markdown</code> (requests with <code>text/markdown;q=0</code> are ignored).</li>
<li>Or the URL includes the query argument <code>output_format=md</code> (handy for browsers and manual testing).</li>
</ul>
</li>
<li>HTML to Markdown — Rendered post body is passed through WordPress’s <code>the_content</code> filters, then converted to Markdown using the <a href="https://github.com/thephpleague/html-to-markdown" rel="nofollow ugc">league/html-to-markdown</a> library. A short YAML front matter block includes <code>title</code> and <code>permalink</code>.</li>
<li>Password-protected content — If a password is required, the response is a small Markdown message instead of the full body.</li>
<li>Discovery in HTML — On the normal HTML view, the plugin prints <code><link rel="alternate" type="text/markdown" href="…?output_format=md" /></code> so clients can find the Markdown URL.</li>
<li>Admin shortcut — On the posts and pages list screens, a row action View as AI Agent opens the same Markdown URL (preview URLs are used for drafts where WordPress would show Preview).</li>
</ul>
Developer filters
<ul>
<li><code>kolibia_ar_markdown_post_types</code> — Defaults to all public, built-in post types from core; override to add custom post types or remove types (e.g. <code>attachment</code>).</li>
<li><code>kolibia_ar_post_markdown</code> — Filter the final Markdown string.</li>
<li><code>kolibia_ar_home_markdown</code> — Filter the Markdown for the posts index / homepage loop.</li>
<li><code>kolibia_ar_home_markdown_post_types</code> — Post types included in the homepage Markdown list (default: <code>post</code>).</li>
<li><code>kolibia_ar_markdown_password_required</code> — Filter the Markdown shown when a password is required.</li>
</ul>
Roadmap
Further “agent readiness” features (broader API discovery, additional formats) may be added in future releases.

Kolibia Agent-Ready

Kolibia Agent-Ready adds API discovery and Markdown responses so AI agents can use your WordPress content and services.

Mescio for Agents vs Kolibia Agent-Ready