outsurface

OutSurface Agent View creates a parallel, lightweight version of your entire website specifically optimized for AI agents and LLM-based automation tools.
Why? Modern websites are built for humans — heavy CSS, JavaScript, images, and visual complexity cost AI agents many tokens to parse, slow down navigation, and make it hard to identify actionable elements. OutSurface Agent View solves this.
Features:
<ul>
<li>Agent-optimized pages at <code>/agent-view/*</code> — same content, no visual overhead</li>
<li>WPBakery, Elementor & Gutenberg — all editor markup stripped, pure content only</li>
<li>Full navigation with submenus — mirrors your WordPress menus hierarchically</li>
<li>Actions prominently displayed — agents can see exactly what they can do on each page</li>
<li>WooCommerce support — Shop, Product (with variants), Cart, Checkout, My Account all agent-ready</li>
<li>Add-to-cart URLs — agents can add products to cart via direct GET links, no forms needed</li>
<li>llm.txt — full site content as plain text at <code>/llm.txt</code> following the llms.txt convention</li>
<li>data.json — complete structured site data at <code>/agent-view/data.json</code></li>
<li>Invisible discovery nav — every human page includes meta tags and HTTP headers so agents can find the agent view</li>
<li>OutSurface account — optional license connection to verify your installation</li>
<li>Debug mode — makes the agent nav visible for your own testing</li>
<li>Description box — tell agents what your site does and what they can accomplish</li>
<li>Low token cost — monospaced, structured, no decorative content</li>
</ul>

OutSurface Agent View

Creates an AI-agent-optimized view of your WordPress site at /agent-view/ — plain text, clear actions, minimal tokens, WooCommerce ready.

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.

OutSurface Agent View vs Kolibia Agent-Ready