How it works
Make the existing WordPress site ready for AI agents
Open for Agents is the WordPress control layer for the machine-readable web. It gives operators one reviewed capability catalog for deciding what agents may understand, discover, or use.
One catalog, four delivery layers
- Human web: semantic HTML, navigation, schema, and sitemaps remain the public foundation.
- Machine-readable understanding:
llms.txt, Markdown alternates, Agent Skills, and readiness metadata explain the site to agents. - Capability discovery: ActionMap, API Catalog, MCP Server Card, and ARD publish approved ways to find resources.
- Controlled execution: MCP and browser-runtime tools retain transactional consent, exact approval, replay protection, and Undo where a reversible change is allowed.
These are adapters over one reviewed canonical WordPress catalog, not separate engines with separate configuration. ARD sits before invocation and helps agents find capabilities; MCP and WebMCP can expose approved ways to use them.
After discovery, the site still has to work
Search visibility helps an agent find a website. Open for Agents focuses on what happens after arrival, when the agent needs to help a person use the active WordPress site safely.
Discovery, Understanding, Usage
Discovery
Agents need reliable entry points: sitemaps, robots rules,llms.txt, well-known files, schema, and public endpoints that describe what the site intentionally exposes.
Understanding
Once an agent is on the page, it needs clear rendered content, semantic structure, accessible labels, stable layout, and validation that confirms the public site matches the WordPress configuration.
Usage
For approved capabilities, deterministic tools are more reliable than forcing an agent to infer a workflow from screenshots, DOM structure, and clicks. Open for Agents starts with reviewed read-only capabilities, while higher-impact workflows stay behind explicit review.
Surfaces the plugin creates
The plugin is built around explicit site surfaces rather than hoping agents infer site behavior from theme markup. Public surfaces include Open for Agents REST endpoints, well-known discovery files,llms.txt, and browser-runtime metadata for compatible agent clients.
Content, forms, and commerce
Open for Agents applies one review and publication model across three first-class WordPress use cases.
- Content: posts, navigation, search, taxonomies, site information, and public discovery form the read-only baseline.
- Forms: eligible Contact Form 7 and WPForms Lite workflows can be discovered and reviewed. Certified execution is limited to supported single-page forms, remains off by default, is enabled for an exact form, and is irreversible after the visitor approves its exact arguments.
- Commerce: WooCommerce product discovery and comparison can remain read-only, while selected cart tools require visitor approval. Checkout, payment, orders, login, and accounts are excluded.
See the Integrations matrix for provider maturity, defaults, tested versions, and limitations.
WebMCP is an emerging browser standard
Chrome 149+ includes a live WebMCP origin trial for enrolled origins. Open for Agents can publish reviewed page tools through that native browser surface while treating the WebMCP specification as pre-standard and subject to change. The operational Open for Agents runtime and hosted demo do not depend on native WebMCP.
See the Live WordPress Demo for hosted examples of page-specific actions, public discovery, and the current Chrome origin-trial behavior.
Safety model
Defaults are conservative. Public publishing is explicit, read-only understanding is the baseline, and uncertain or higher-impact workflows stay behind review. The product validates technical capability by checking the public surfaces a WordPress site intentionally exposes.
Operator workflow
- Install the plugin and start from conservative defaults.
- Review the generated surfaces and safety flags.
- Validate public URLs through the real host, cache, and CDN.
- Publish only the surfaces you approve.
- Revalidate after host, plugin, or policy changes.
Public validation matters
WordPress configuration can look correct locally while public traffic still fails because of redirects, blocked well-known paths, cached responses, proxy rules, or host security defaults. Open for Agents treats public validation as part of the product, not an afterthought.