Kolibia Agent-Ready vs Markdown for Agents and Statistics

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 Markdown for Agents on Cloudflare): clients that prefer Markdown can request it explicitly. What is included today Markdown responses for singular content — For each built-in public post type registered by WordPress core (post, page, attachment on a typical site), a single-item URL can return Content-Type: text/markdown; charset=UTF-8 instead of the themed HTML page. 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. Static or WooCommerce shop front page — When a page is set as the front page (including a WooCommerce shop page where WordPress reports is_singular as false), that page’s content is still served as Markdown on / when clients negotiate text/markdown. When Markdown is served The request includes an Accept header that lists text/markdown (requests with text/markdown;q=0 are ignored). Or the URL includes the query argument output_format=md (handy for browsers and manual testing). HTML to Markdown — Rendered post body is passed through WordPress’s the_content filters, then converted to Markdown using the league/html-to-markdown library. A short YAML front matter block includes title and permalink. Password-protected content — If a password is required, the response is a small Markdown message instead of the full body. Discovery in HTML — On the normal HTML view, the plugin prints so clients can find the Markdown URL. 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). Developer filters kolibia_ar_markdown_post_types — Defaults to all public, built-in post types from core; override to add custom post types or remove types (e.g. attachment). kolibia_ar_post_markdown — Filter the final Markdown string. kolibia_ar_home_markdown — Filter the Markdown for the posts index / homepage loop. kolibia_ar_home_markdown_post_types — Post types included in the homepage Markdown list (default: post). kolibia_ar_markdown_password_required — Filter the Markdown shown when a password is required. Roadmap Further “agent readiness” features (broader API discovery, additional formats) may be added in future releases.

Markdown for Agents and Statistics converts your WordPress content to Markdown and serves it to AI agents and language model tools that request it via HTTP content negotiation (Accept: text/markdown). The Chancery Lane Project is a charity that helps organisations reduce emissions using the power of legal documents and processes. We’ve published this plugin as we believe that making content more legible for AI Agents makes a meaningful difference to their energy usage – not only by reducing the amount of tokens required (by up to 90% over HTML) to consume the content, but also minimising the server resources required to render, process and display pages at source. How it works: Posts and taxonomy archive pages are converted to Markdown and saved as static files on disk inside wp-content/uploads/. When a visitor (or AI agent) requests a page with Accept: text/markdown in the HTTP headers, WordPress serves the pre-generated .md file directly — no page render required. A tag is added to each page’s so agents can discover Markdown versions automatically. Features: Content negotiation (Accept: text/markdown, ?output_format=md, or known AI User-Agents) Taxonomy archive support — category, tag, and custom taxonomy term pages served as Markdown post listings Automatic Markdown generation on post save; taxonomy archives auto-update when any post in the term changes Background bulk generation — runs as a WP-Cron job with live progress, so it survives closing the tab and never times out a page request Per-post-type field configuration — choose which meta/ACF fields go in frontmatter or body ACF support with dot notation for nested group fields (e.g. group.subfield) Content fields option — use ACF fields as the body content instead of post_content Manifest generation with content hashes and change tracking per post type Incremental export — only re-export changed documents (--incremental) Delta file (changes.json) for RAG system sync Access statistics — logs AI agent requests with a dedicated stats admin page Access grouping by class of agent Optional frontmatter fields — hierarchy (parent/ancestors/children IDs), author display name, root-relative featured image paths Topics section — appends a ## Topics section with linked taxonomy terms to the Markdown body Export preview — preview generated Markdown inline in the post editor without writing to disk OKF directory indexes — index.md listings at the export root and in every post-type and taxonomy directory (Open Knowledge Format), kept current automatically OKF-compliant frontmatter and links — timestamp and flat cross-taxonomy tags frontmatter keys, and internal links rewritten to point at the Markdown file versions, always on Downloadable OKF bundle — optional .zip archive of the export tree with relative internal links, manifest.json, and an ARD discovery catalog panel, kept fresh via bulk-generation rebuilds and a debounced WP-Cron schedule ARD catalog generation — ai-catalog.json document for manual deployment to /.well-known/, discoverable by AI agent directories, shown automatically whenever the bundle toggle is on WP-CLI commands: generate, generate-taxonomies, generate-indexes, prune-stats, status, delete, bundle Fully unit-tested