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.

Selvakumar Duraipandian

Markdown for AI Agents is a lightweight WordPress plugin that enables HTTP content negotiation for your site’s content. When a client (like an AI agent or a custom script) requests a page with the <code>Accept: text/markdown</code> header, the plugin intercepts the request and returns a clean, structured Markdown representation of the post or page content.
This is ideal for AI crawlers, RAG (Retrieval-Augmented Generation) systems, and non-browser clients that prefer machine-friendly text over complex HTML.
Important note: This plugin is primarily a developer/integration tool. Human visitors browsing your site will never see any difference — the Markdown output is only served when explicitly requested via the <code>Accept: text/markdown</code> HTTP header. Normal browser requests always receive the standard HTML page.
Key Features:
<ul>
<li>Automatically detects <code>Accept: text/markdown</code> headers.</li>
<li>Converts HTML content to clean Markdown using the League HTMLToMarkdown library.</li>
<li>Strips away theme layout, navigation, headers, footers, and sidebars — serving only the main content.</li>
<li>Adds useful HTTP response headers: <code>Content-Type: text/markdown</code>, <code>Vary: Accept</code>, and <code>X-Markdown-Word-Count</code>.</li>
<li>Respects WordPress visibility rules and filters.</li>
<li>No configuration required — works out of the box for posts, pages, and custom post types.</li>
</ul>
<h3>How It Works</h3>
This plugin uses a standard web technique called HTTP content negotiation. The same URL on your site can serve different representations of the same content depending on what the client asks for:
<ul>
<li>A regular browser sends <code>Accept: text/html</code> → receives your normal HTML page.</li>
<li>An AI agent sends <code>Accept: text/markdown</code> → receives a clean Markdown version of the same page.</li>
</ul>
No extra URLs, no duplicate content, no configuration needed. The plugin hooks into WordPress’s <code>template_redirect</code> action, detects the <code>Accept</code> header, captures the rendered HTML, converts it to Markdown, and returns it with appropriate headers.
<h3>Why Markdown for AI Agents?</h3>
When building RAG (Retrieval-Augmented Generation) applications or AI pipelines that ingest web content, HTML is extremely noisy. A typical WordPress page contains thousands of tokens worth of HTML tags, inline styles, navigation menus, scripts, and layout markup — none of which carries meaning for an AI model.
Serving clean Markdown instead can reduce token consumption by up to 60%, which means:
<ul>
<li>Lower API costs — fewer tokens ingested when loading pages into vector stores or LLM pipelines.</li>
<li>Faster processing — less text for the model to parse, filter, and discard.</li>
<li>Better retrieval accuracy — higher signal-to-noise ratio improves the quality of RAG results.</li>
<li>Simpler pipelines — no need for custom HTML stripping logic on the client side; the plugin handles it server-side.</li>
</ul>
Any AI agent, crawler, or ingestion script that sends <code>Accept: text/markdown</code> in its request header will automatically receive the clean Markdown version — no extra URLs, no separate endpoints, no changes to your content workflow.

Markdown for AI Agents

Serve clean Markdown versions of WordPress content to AI agents using HTTP content negotiation.

Kolibia Agent-Ready vs Markdown for AI Agents