skswave

When an AI agent visits your WordPress site today, it has to scrape HTML, guess your organization, and parse legal pages written for humans. Rootz AI Discovery fixes this by serving structured, machine-readable data that AI agents can understand instantly.
What it does:
<ul>
<li>Serves <code>/.well-known/ai</code> with your organization identity, capabilities, and policies (RFC 8615)</li>
<li>Structured content endpoint at <code>/.well-known/ai/content</code> with pages, posts, media, custom types</li>
<li>Auto-generates knowledge base at <code>/.well-known/ai/knowledge</code></li>
<li>AI-optimized content feed at <code>/.well-known/ai/feed</code></li>
<li>Machine-readable policies at <code>/.well-known/ai/policies</code></li>
<li>Adds <code><link rel="ai-discovery"></code> tag and HTTP Link header to every page</li>
<li>Generates <code>/llms.txt</code> from your site structure</li>
<li>Provides REST API endpoints for AI agents (<code>/wp-json/rootz/v1/</code>)</li>
<li>Registers WebMCP tools for browser-based AI assistants</li>
<li>Machine-readable content licensing (CC-BY, CC0, All Rights Reserved, etc.)</li>
<li>AI training opt-in/opt-out declaration</li>
<li>Cryptographic signing — every ai.json response and llms.txt is digitally signed (ECDSA secp256k1), proving origin and content integrity</li>
<li>Digital identity via plugin wallet (Ethereum-compatible address generated locally)</li>
<li>Content assertion types (factual, editorial, creative-work) per item</li>
<li>AI access metrics and analytics dashboard</li>
<li>Self-scoring status endpoint for monitoring</li>
</ul>
Signed for origin and quality. Each plugin install generates a unique cryptographic identity. Every manifest is digitally signed so AI agents can verify the data came from your site and hasn’t been tampered with. No other WordPress plugin does this. For more information on managing your digital identity, see <a href="https://rootz.global/identity" rel="nofollow ugc">rootz.global/identity</a>.
Core data is generated locally from your existing WordPress content. Optional AI-powered features use external services (see Third-Party Services below).
Open standard. The AI Discovery Standard is CC-BY-4.0 licensed. See <a href="https://rootz.global/ai-discovery" rel="nofollow ugc">rootz.global/ai-discovery</a>.
<h4>Third-Party Services</h4>
This plugin connects to external services in the following cases. All connections use HTTPS.
1. Rootz AI Proxy (optional) 
When you use the “Auto-Populate with AI” feature to generate your site description, summary, or core concepts, the plugin sends your site URL and basic metadata to: 
* Service: <code>dev.epistery.host/agent/rootz/ai-proxy/</code> 
* Data sent: Site URL, title, tagline 
* When: Only when you click “Auto-Populate” in the admin panel 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
2. Anthropic API (optional) 
If you enter your own Anthropic API key in settings, the plugin can call the Anthropic API directly as a fallback for AI content generation: 
* Service: <code>api.anthropic.com</code> 
* Data sent: Site URL, title, tagline (same as above) 
* When: Only when you click “Auto-Populate” and have entered an API key 
* Privacy: See https://www.anthropic.com/legal/privacy
3. Plugin Updates (automatic) 
The plugin checks for available updates from the Rootz update server: 
* Service: <code>rootz.global/api/plugin/update.json</code> 
* Data sent: None (read-only GET request) 
* When: Automatically every 12 hours (uses WordPress transients) 
* Note: Disabled when the plugin is installed from WordPress.org (WP.org provides updates instead) 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
4. License Verification (automatic when configured) 
If you enter an Owner Identity in the Account tab, the plugin verifies your subscription status: 
* Service: <code>rootz.global/api/license/status</code> 
* Data sent: Your Owner Identity address (a public blockchain address, not personal data) 
* When: On admin page load, cached for 12 hours 
* Privacy: <a href="https://rootz.global/privacy" rel="nofollow ugc">rootz.global/privacy</a>
<h3>Privacy</h3>
<h4>Data Storage</h4>
All structured data (organization identity, policies, content) is generated from your existing WordPress content and stored in wp_options. No user data is collected.
<h4>External Services</h4>
The plugin connects to external services only when specific features are used. See the “Third-Party Services” section in the Description tab for complete details including what data is sent, when, and links to each service’s privacy policy.
<h4>Cookies</h4>
This plugin does not set any cookies.
<h4>Analytics</h4>
The plugin tracks AI agent visits to your /.well-known/ai endpoints in a local database table (wp_rootz_metrics). This data stays on your server and is never transmitted externally. You can view it in the Analytics tab.

Rootz AI Discovery

Make your WordPress site AI-agent-ready. Structured identity, policies, content API, and WebMCP tools at /.well-known/ai.

Matthias Pfefferle

This plugin enables “Well-Known URIs” support for WordPress (RFC 5785: http://tools.ietf.org/html/rfc5785).
From the RFC:
It is increasingly common for Web-based protocols to require the 
 discovery of policy or other information about a host (“site-wide 
 metadata”) before making a request. For example, the Robots 
 Exclusion Protocol <a href="http://www.robotstxt.org/" rel="nofollow ugc">http://www.robotstxt.org/</a> specifies a way for 
 automated processes to obtain permission to access resources; 
 likewise, the Platform for Privacy Preferences 
 tells user-agents how to discover privacy policy beforehand.
While there are several ways to access per-resource metadata (e.g., 
 HTTP headers, WebDAV’s PROPFIND [RFC4918]), the perceived overhead 
 (either in terms of client-perceived latency and/or deployment 
 difficulties) associated with them often precludes their use in these 
 scenarios.
When this happens, it is common to designate a “well-known location” 
 for such data, so that it can be easily located. However, this 
 approach has the drawback of risking collisions, both with other such 
 designated “well-known locations” and with pre-existing resources.
To address this, this memo defines a path prefix in HTTP(S) URIs for 
 these “well-known locations”, “/.well-known/”. Future specifications 
 that need to define a resource for such site-wide metadata can 
 register their use to avoid collisions and minimise impingement upon 
 sites’ URI space.

/.well-known/

This plugin enables "Well-Known URIs" support for WordPress

Rootz AI Discovery vs /.well-known/