aiMiles – AI Agent vs Mescio for Agents

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.

Mescio for Agents 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 Accept: text/markdown content negotiation header. Human visitors using a browser are completely unaffected. Mescio for Agents only activates when an AI agent or crawler explicitly asks for Markdown. Why Markdown? Feeding raw HTML to an AI is expensive and noisy. A heading like ## About Us costs ~3 tokens in Markdown vs 12–15 tokens as HTML — before accounting for 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. Markdown has become the lingua franca for AI systems. Mescio for Agents lets your site speak it natively, at zero cost to your human visitors. How it works When an HTTP client sends a request with Accept: text/markdown, 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 Content-Type: text/markdown header. curl https://yoursite.com/your-post/ \ -H "Accept: text/markdown" Features Zero configuration — works out of the box on any singular post, page or custom post type /llms.txt endpoint — auto-generated index of all your content in the llmstxt.org standard format, so AI agents can discover what’s on your site /llms-full.txt endpoint — full site content in a single Markdown file, ready for RAG pipelines WooCommerce support — product pages include price, SKU, stock status, rating, attributes and gallery; products are grouped by category in llms.txt YAML front matter — every document includes structured metadata (title, description, URL, date, categories, tags, featured image) Multilingual — detects language via WPML, Polylang, TranslatePress or WordPress locale; emits Content-Language and Link: rel=alternate headers REST API endpoint — /wp-json/mescio-for-agents/v1/markdown?id= or ?url= Page builder cleanup — aggressively strips Elementor, Divi, WPBakery and Beaver Builder layout noise Token count header — X-Markdown-Tokens tells AI pipelines how large the document is before processing Content Signals — emits Content-Signal: ai-train=yes, search=yes, ai-input=yes Correct HTTP caching — Vary: Accept ensures CDNs cache HTML and Markdown versions separately Response headers Content-Type: text/markdown; charset=utf-8 Content-Language: it (or detected language) Vary: Accept X-Markdown-Tokens: 725 Content-Signal: ai-train=yes, search=yes, ai-input=yes Link: ; rel="alternate"; hreflang="en" (when translations available) Multilingual plugin support WPML — reads language and available translations automatically Polylang — reads language and links to translated post IDs TranslatePress — reads trp_language post meta Manual — configure primary language and additional languages in Settings → Mescio for Agents REST API GET /wp-json/mescio-for-agents/v1/markdown?id=42 GET /wp-json/mescio-for-agents/v1/markdown?url=https://yoursite.com/my-page/ Developer hooks Filter: mescio_enabled_post_types — add or remove post types dynamically. Filter: mescio_pre_convert_content — modify the HTML before conversion to Markdown. Filter: mescio_post_convert_content — modify the Markdown after conversion. Privacy This plugin does not collect, store or transmit any personal data. It does not set cookies. It does not make external HTTP requests.