Content
Posts, navigation, search, taxonomies, and public discovery through a read-only baseline.
WordPress tools + live AI Assistant
Make WordPress usable by AI agents.
Give AI agents reviewed ways to understand and safely use content, forms, and commerce on your site, under explicit operator control.
The WordPress control layer for the machine-readable web. Review once. Publish safe capabilities across the discovery and execution formats agents use.
The live demo's hosted Assistant works in ordinary modern browsers with no extension or API key. Browser-native WebMCP integration is available for controlled testing as the emerging browser standard evolves.
Real WordPressReviewed content, commerce, and form toolsOperator-controlled publicationHuman-approved writes
Three product pillars
Useful across the WordPress site
Forms
Reviewed lead and contact workflows through Contact Form 7 and WPForms Lite, enabled one form at a time.
Commerce
WooCommerce discovery and comparison, with cart changes kept behind visible visitor approval.
One reviewed source of truth
Review WordPress capabilities once, then publish deliberately
Open for Agents discovers site capabilities, keeps the human website intact, lets an operator choose what may be public or executable, and derives every agent-facing adapter from the same approved WordPress catalog.
Understanding
llms.txt, Markdown alternates, readiness metadata, and Agent Skills help agents interpret the site.
Discovery
ActionMap, API Catalog, MCP Server Card, and the ARD AI Catalog help agents find approved capabilities.
Execution
MCP and WebMCP expose reviewed tools, while consent, exact approval, replay protection, and Undo govern changes.
ARD helps agents find capabilities. MCP and the emerging WebMCP browser standard help agents use approved capabilities. Open for Agents supplies the WordPress governance, validation, and safety layer behind both.
Flagship live demo
Give an agent a real storefront task
The Storefront Assistant searches and compares real WooCommerce data, then keeps cart changes behind visible visitor approval.
Storefront Assistant
Ask, compare, approve, and undo
Use an embedded AI Assistant on a real WooCommerce store. Ask it to find products, compare choices, inspect the cart, or request a cart change through the WordPress tools on the page.
- Searches and compares a real WooCommerce catalog
- Requires visitor approval before cart changes
- Includes Undo, Redo, Reset cart, and visible tool activity
Works in an ordinary modern browser. No extension or API key required.
Try the Storefront AssistantSupported integrations
Commerce is the live proof, not the product boundary
Contact Form 7 and WPForms Lite provide the launch forms compatibility set. Detection, reviewed public output, and transactional execution remain separate capability levels.
WooCommerce
Read-only product discovery plus reviewed, approval-gated cart tools.
WPForms Lite
Form discovery plus native reviewed submission for supported single-page forms.
Contact Form 7
Form discovery plus native reviewed submission through the provider pipeline.
Certified execution is limited to supported single-page forms. Transactions are off by default and enabled one reviewed form at a time. The visitor approves the exact arguments before an irreversible submission; payment, uploads, login, accounts, and other sensitive form scenarios are excluded.
Product workflow
From an ordinary site to reviewed agent tools
Open for Agents separates discovery, understanding, and usage, then gives operators a repeatable path from install to publication.
Discovery
Help agents find the site, identify its purpose, and locate approved machine-readable surfaces through sitemaps, well-known files, schema, and llms.txt.
Understanding
Make the active WordPress page clear through explicit content, semantic structure, accessible labels, stable rendering, and public validation.
Usage
Give agents reviewed, deterministic ways to use approved site capabilities instead of relying on fragile UI clicking or guessed workflows.
[ 01 ]
Set up
Start from conservative read-only defaults, then choose the capabilities that belong on the active WordPress site.
[ 02 ]
Review
Review the public capabilities, safety flags, and generated surfaces before anything becomes authoritative.
[ 03 ]
Validate
Run diagnostics against the public URLs agents will use, including well-known paths, REST routes, and browser runtime output.
[ 04 ]
Publish
Publish only reviewed surfaces. Sensitive, high-risk, or uncertain capabilities stay private, and approved mutations retain their visitor controls.
[ 05 ]
Live
Give agents a stable way to understand the existing site, and keep validating it as host configuration, caching, and plugin behavior change.
Arrival is only the start. Search can help an agent find your site. The next problem is whether the active WordPress site is clear enough for the agent to help the user.
Exposure needs limits. Making a site useful to agents should not mean exposing every form, route, selector, or admin-adjacent surface that happens to exist.
Host behavior matters. A local plugin check is not enough. Your public endpoints must survive the real host, cache, CDN, redirects, and security configuration agents will actually encounter.
Inside the plugin
One coherent review and publication flow
Move from the effective catalog to review, validation, and deliberate publication without losing the source or safety context.
Dashboard
Start with the effective catalog
See the capabilities available on the active WordPress site and the checks that still need attention.
Operator control
Useful to agents, accountable to people
Public discovery is opt-in. Read-only capabilities form the safe baseline, while state-changing actions remain explicit and reviewable.
Conservative by default
Start with safe read-only understanding. State-changing workflows require explicit review and visible visitor approval before execution.
Publishing is explicit
Public agent-ready surfaces are opt-in. If publishing is disabled, public endpoints should not pretend to be available.
No pretend publishing
If a surface is not ready for visitors or agents, it stays unpublished until it can say something real.
Validation-first
Checks report what is present, missing, or blocked so operators can fix their setup before publishing.
Controlled content visibility
Content, navigation, taxonomy, and product catalog data can be made clear to agents through explicit read-only surfaces.
Reduced silent failure
Diagnostics help catch blocked routes, stale cache behavior, missing well-known files, and CDN rules that would otherwise fail outside the WordPress admin.
Operator control
The site owner chooses what is public. The goal is useful agent support, not broad exposure of every possible interaction.
Verified public presence
Published sites can show agents what they intentionally make available, with validation before those surfaces are shared.
Built for real WordPress work
For publishers, stores, service businesses, and agencies
Publishers and content sites
Expose posts, navigation, search, taxonomies, and public discovery through explicit, validated read-only surfaces.
WooCommerce stores
Make product discovery and comparison clear while keeping reviewed cart changes behind visitor approval.
Lead-generation sites
Review eligible enquiry and contact forms individually before visitors can approve an irreversible submission.
Agencies and developers
Apply one explainable readiness model across mixed content, commerce, and service-business WordPress estates.
Built by a WordPress publisher
Enoki Limited has published on WordPress for 20 years. Open for Agents grew from the need for agent-facing behavior that is specific, conservative, and testable on real sites.
Read the product storyProduct updates
Follow the path to a public release
Get practical updates on making WordPress clearer and safer for AI agents as the plugin moves toward a public release.
Prefer context first? Read the Getting Started guide, inspect the demo discovery JSON, or email hello@openforagents.com.
We respect your privacy. See our privacy policy.