Mescio for Agents vs JWT Authentication for WP REST APIs

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.

WordPress REST API endpoints are open and unsecured by default which can be used to access your site data. Secure WordPress APIs from unauthorized users with our JWT Authentication for WP REST APIs plugin. Our plugin offers below authentication methods to Protect WP REST API endpoints: – JWT Authentication – Basic Authentication – API Key Authentication – OAuth 2.0 Authentication – External Token based Authentication 2.0/OIDC/JWT/Firebase provider’s token authentication methods. You can authenticate default WordPress endpoints and custom-developed REST endpoints and third-party plugin REST API endpoints like that of Woocommerce, Learndash, Buddypress, Gravity Forms, CoCart, etc. WP REST API Authentication Methods in our plugin JWT Authentication Provides an endpoint where you can pass the user credentials, and it will generate a JWT (JSON Web Token), which you can use to access the WordPress REST APIs accordingly. Additionally, to maintain a seamless user experience without frequent logins needed due to token expiry, you can use our Refresh and Revoke token mechanisms feature. When the access token expires, instead of forcing the user to log in again, the client can request a new access token using a valid refresh token. API Key Authentication Basic Authentication: – 1. Username: Password – 2. Client-ID: Client-Secret OAuth 2.0 Authentication – 1. Password Grant – 2. Client Credentials Grant Third Party Provider Authentication Following are some of the integrations that are possible with WP REST API Authentication: Learndash API Authentication Custom Built REST API Endpoints Authentication BuddyPress API Authentication WooCommerce API Authentication Gravity Form API Authentication External/Third-party plugin API endpoints integration in WordPress You can also disable the WP REST APIs with our plugin such that no one can make API calls to your WordPress REST API endpoints.Our plugin also provides Refresh and Revoke Token that can be used to improve the API security. Benefits of Refresh Token Enhances security by keeping access tokens short-lived. Improves user experience with uninterrupted sessions. Reduces login frequency. Benefits of Revoke Token Protects against token misuse if a device is lost or compromised. Enables admin-triggered logouts or session control. Useful for complying with stricter session policies. With this plugin, the user is allowed to access your site’s resources only after successful WP REST API authentication. JWT Authentication for WP REST APIs plugin will make your WordPress endpoints secure from unauthorized access. Plugin Feature List FREE PLAN Authenticate only default core WordPress REST API endpoints. Basic Authentication with username and password. JWT Authentication (JSON Web Token Authentication). Enable Selective API protection. Restrict non-logged-in users to access REST API endpoints. Disable WP REST APIs PREMIUM PLAN Authenticate all REST API endpoints (Default WP, Custom APIs,Third-Party plugins) JWT Token Authentication (JSON Web Token Authentication) Login, Refresh and Revoke token endpoints for token management API Key Authentication Basic Authentication (username/password and email/password) OAuth 2.0 Authentication Universal API key and User-specific API key for authentication Selective API protection. Disable WP REST APIs Time-based token expiry Role-based WP REST API authentication Custom Header support rather than just Authorization to increase security. Create users in WordPress based on third-party provider access tokens (JWT tokens) authentication. Privacy This plugin does not store any user data.