David Perez

closemarketing

Alex Brea

<p>Knowledge Base Chatbot helps you curate the exact content you want to use as a “knowledge base” and generates a single Markdown file (<code>llm-knowledge-chatbot.md</code>) that can be consumed by an external chatbot or LLM pipeline.</p>
<p>From the WordPress admin, you can:</p>
<ul>
<li>Select content from any public post type that is available in the admin (Pages, Posts, and most custom post types).</li>
<li>Add selected items to a curated list.</li>
<li>Reorder the list via drag & drop.</li>
<li>Regenerate the Markdown file at any time (it is also regenerated automatically after adding/removing items).</li>
</ul>
<p>The generated file is saved in your WordPress root folder and can be accessed via a public URL such as:<br />
    https://example.com/llm-knowledge-chatbot.md</p>


Knowledge Base Chatbot

Generate a Markdown knowledge base file from selected WordPress content (pages, posts, and CPTs) to power an external chatbot/LLM workflow.

Mescio

<p><strong>Mescio for Agents</strong> 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.</p>
<p>Human visitors using a browser are <strong>completely unaffected</strong>. Mescio for Agents only activates when an AI agent or crawler explicitly asks for Markdown.</p>
<h4>Why Markdown?</h4>
<p>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.</p>
<p>Markdown has become the <em>lingua franca</em> for AI systems. Mescio for Agents lets your site speak it natively, at zero cost to your human visitors.</p>
<h4>How it works</h4>
<p>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.</p>
<pre><code>curl https://yoursite.com/your-post/ \
  -H "Accept: text/markdown"
</code></pre>
<h4>Features</h4>
<ul>
<li><strong>Zero configuration</strong> — works out of the box on any singular post, page or custom post type</li>
<li><strong><code>/llms.txt</code> endpoint</strong> — 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><strong><code>/llms-full.txt</code> endpoint</strong> — full site content in a single Markdown file, ready for RAG pipelines</li>
<li><strong>WooCommerce support</strong> — product pages include price, SKU, stock status, rating, attributes and gallery; products are grouped by category in <code>llms.txt</code></li>
<li><strong>YAML front matter</strong> — every document includes structured metadata (title, description, URL, date, categories, tags, featured image)</li>
<li><strong>Multilingual</strong> — detects language via WPML, Polylang, TranslatePress or WordPress locale; emits <code>Content-Language</code> and <code>Link: rel=alternate</code> headers</li>
<li><strong>REST API endpoint</strong> — <code>/wp-json/mescio-for-agents/v1/markdown?id=<post_id></code> or <code>?url=<permalink></code></li>
<li><strong>Page builder cleanup</strong> — aggressively strips Elementor, Divi, WPBakery and Beaver Builder layout noise</li>
<li><strong>Token count header</strong> — <code>X-Markdown-Tokens</code> tells AI pipelines how large the document is before processing</li>
<li><strong>Content Signals</strong> — emits <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code></li>
<li><strong>Correct HTTP caching</strong> — <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><strong>WPML</strong> — reads language and available translations automatically</li>
<li><strong>Polylang</strong> — reads language and links to translated post IDs</li>
<li><strong>TranslatePress</strong> — reads <code>trp_language</code> post meta</li>
<li><strong>Manual</strong> — configure primary language and additional languages in Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> 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>
<p><strong>Filter: <code>mescio_enabled_post_types</code></strong> — add or remove post types dynamically.</p>
<p><strong>Filter: <code>mescio_pre_convert_content</code></strong> — modify the HTML before conversion to Markdown.</p>
<p><strong>Filter: <code>mescio_post_convert_content</code></strong> — modify the Markdown after conversion.</p>
<h4>Privacy</h4>
<p>This plugin does not collect, store or transmit any personal data. It does not set cookies. It does not make external HTTP requests.</p>


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.

Knowledge Base Chatbot vs Mescio for Agents