# Open for Agents > Open for Agents helps website owners choose what to publish for compatible AI agents, observe how public routes respond over HTTP, and keep visitors in control of any changes. Open for Agents Core is the WordPress plugin. It discovers, reviews, validates, and publishes approved capabilities across content and public discovery, reviewed Contact Form 7 and WPForms Lite workflows, and WooCommerce discovery with approval-gated cart changes. Its public outputs come from the same owner-reviewed WordPress catalogue. Understanding formats include llms.txt, Markdown alternates, readiness metadata, and Agent Skills. Discovery formats include ActionMap, API Catalog, MCP Server Card, and ARD AI Catalog. Core's current Streamable HTTP MCP endpoint is read-only. Separately reviewed WebMCP and Assistant operations may include a state change behind their own authorization and exact visitor approval. Open for Agents for Shopify is a free, read-only catalogue-assurance app. It compares Shopify Admin intent, supported AI shopping catalogue output, and public-store evidence; it does not govern Shopify's agent infrastructure or change store data. This llms.txt file is an optional compatibility resource for agent clients that choose to read it. It is not a Google Search inclusion or ranking signal; crawlable, useful HTML, indexing, and normal SEO remain the Search foundation. Download Core 0.3.54 for free from WordPress.org. It requires no Open for Agents account, AI API key, paid licence, or hosted service. Open for Agents Assistant 0.1.11 is a separate add-on and is not bundled in the WordPress.org Core package. You can try the official demo in your browser. We provide the Assistant add-on and managed service directly for selected projects; there is no public download or self-service plan yet. The live demo publishes an ARD AI Catalog that conforms to the current draft. This does not imply universal registry listing, cryptographic identity, or OKF support. ## Product and documentation - [Product overview](https://www.openforagents.com/): WordPress plugin, safety controls, and the live Storefront Assistant. - [Why agent-ready websites now](https://www.openforagents.com/why-agent-ready): Browser agents, WebMCP, owner governance, direct access, the optional Assistant, and current limitations. - [Open for Agents Assistant](https://www.openforagents.com/assistant): Visitor experience, Core/add-on/hosted-service relationship, exact approval, boundaries, and who can use it. - [Website Visibility Check](https://www.openforagents.com/visibility): Enter a public website for a live, read-only check of page access, readable content, crawler rules, sitemap, llms.txt, and agent-readiness details. - [WordPress Agent Readiness Assessment](https://www.openforagents.com/wordpress/agency-readiness): A human-reviewed, one-site comparison of owner intent, Core publication, public evidence, MCP and WebMCP with an exact developer handoff and follow-up comparison. - [Connect an AI app](https://www.openforagents.com/connect): Use the same read-only Website Visibility Check from a compatible AI app through the hosted Open for Agents MCP server. - [MCP, WebMCP, or both?](https://www.openforagents.com/docs/mcp): Choose between remote MCP and page-attached WebMCP tools, understand what each test result establishes, and connect the hosted Visibility Check. - [How it works](https://www.openforagents.com/how-it-works): Discovery, understanding, usage, publication, and validation model. - [Documentation](https://www.openforagents.com/docs): Setup, integrations, Assistant configuration, action types, publication tiers, terminology, and troubleshooting. - [Integrations](https://www.openforagents.com/docs/integrations): Form-provider detection and field discovery, which forms can be published or submitted, defaults, tested versions, and limitations. - [Live WordPress demos](https://www.openforagents.com/demo): The Storefront Assistant plus Build-a-Buddy and Cursed Kitchen. - [Open for Agents for Shopify](https://www.openforagents.com/shopify): A free Shopify app for independent read-only catalogue exposure monitoring. - [Try Any-Web](https://www.openforagents.com/demo/any-web): A focused, read-only conversation over reviewed Open for Agents public material with visible source citations. - [References](https://www.openforagents.com/references): Relevant specifications and ecosystem references. - [Install Open for Agents 0.3.54](https://wordpress.org/plugins/open-for-agents-ai-toolkit-with-mcp/): Official WordPress.org plugin listing. - [Try the Open for Agents Live Preview](https://wordpress.org/plugins/open-for-agents-ai-toolkit-with-mcp/?preview=1): Stable WordPress.org preview entry point. - [Watch the 76-second Open for Agents demonstration](https://www.youtube.com/watch?v=G1JDZRRWRBk): Public video walkthrough. ## Directory - [Published site directory](https://www.openforagents.com/directory): Public entries whose listed readiness URLs responded successfully when last checked. - [Directory JSON feed](https://www.openforagents.com/directory/feed.json): Machine-readable directory data. ## Optional - [Stories](https://www.openforagents.com/blog): Product stories, release explanations, and field notes. - [Stories feed](https://www.openforagents.com/blog/feed.xml): Machine-readable Stories feed. - [Rendering is not understanding](https://www.openforagents.com/blog/rendering-is-not-understanding): We tested Kitesurf and Chromium across nine agent-ready pages. Both rendered every page. Chromium also found every WebMCP tool the pages were designed to expose. - [Can one website tool keep the same rules across agent clients?](https://www.openforagents.com/blog/one-capability-many-agent-surfaces): I tested whether a read-only Open for Agents tool kept the same inputs, limits, and permissions when packaged for Agent Plugins 1.0 and used in Codex. - [Cloudflare made WebMCP easier. Website owners still choose the tools.](https://www.openforagents.com/blog/cloudflare-webmcp-website-governance): Cloudflare's WebMCP preview can deliver tools in the browser. Website owners still decide which tools to publish and what agents may do with them. - [Why I built Open for Agents](https://www.openforagents.com/blog/why-i-built-open-for-agents): After more than 20 years as a web publisher, I can see agents changing how people use websites. Owners need a practical way to stay in control. - [Use Open for Agents with Microsoft Agent Framework](https://www.openforagents.com/blog/use-open-for-agents-with-microsoft-agent-framework): Connect Microsoft Agent Framework to a WordPress site's owner-reviewed Open for Agents MCP tools, with practical Python and .NET examples. - [Why now: search agents, browser agents, commerce protocols, and site Assistants](https://www.openforagents.com/blog/why-now-search-browser-commerce-agents): How website owners can decide what emerging search, browser, commerce, and site-provided agents may know and do.