aiMiles – AI Agent vs Kolibia Agent-Ready

aiMiles detects AI agents visiting your WordPress site and allows you to serve them sponsored content. How It Works When any request hits your site, the plugin checks the User-Agent header If it matches a known AI bot signature (25+ supported), the request is routed through the aiMiles serve API The API fetches your original page, appends a sponsored message, and returns the result to the bot Human visitors are never affected — they always see your original, unmodified pages Supported AI Agents GPTBot (OpenAI) ChatGPT-User (OpenAI) ClaudeBot (Anthropic) Claude-Web (Anthropic) PerplexityBot (Perplexity) Google-Extended (Google) Meta-ExternalAgent (Meta) AppleBot-Extended (Apple) ByteSpider (ByteDance) CCBot (Common Crawl) And 15+ more Configuration Enable/Disable Toggle detection and serving on/off. API Key Your aiMiles API key is required. Get one at https://app.aimiles.ai/publishers/settings External services This plugin connects to the aiMiles serve API (https://app.aimiles.ai/api/serve) to proxy AI bot requests. An API key is required to use this service. Data sent to the API When an AI agent is detected visiting your site, the plugin makes a request to https://app.aimiles.ai/api/serve with the following query parameters: url — The full URL the bot was requesting on your site key — Your API key (for authentication) ua — The visitor’s User-Agent header The serve API fetches your original page, appends sponsored content, logs the visit, and returns the modified HTML. This happens on every AI agent page visit. Human visitors are never routed through the API. Service provided by aiMiles: Terms of Service, Privacy Policy.

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.