Discovery is inconsistent
Agents may hit cached pages, blocked well-known paths, theme markup, or plugin output that does not describe the site's intended public contract.
Open for Agents makes WordPress agent-readable.
Give AI agents structured, read-only ways to understand your WordPress site without exposing admin-only paths or hoping a crawler guesses correctly. Validate the public contract through your real host and CDN before you publish it.
Join the launch list for public release notes, host-specific configuration guides, and directory availability.
We respect your privacy. See our privacy policy.
The default WordPress setup is ambiguous to agents
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.
Structured surfaces, conservative defaults
Agent-readable discovery surfaces
Open for Agents creates structured WordPress discovery surfaces including REST endpoints, well-known files, llms.txt, and browser-runtime metadata.
Validated public behavior
Operator-facing diagnostics check that the surfaces agents see from the public web match what WordPress is configured to expose.
How It Works
[ 01 ]
Install
Add Open for Agents to your WordPress site like any other plugin, then start from conservative read-only defaults.
[ 02 ]
Review
Review the public capabilities, safety flags, and generated discovery 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 the read-only surfaces you approve. Sensitive, high-risk, or uncertain capabilities stay private by default.
[ 05 ]
Live
Give agents a stable public contract and keep validating it as host configuration, caching, and plugin behavior change.
See It In Action
Click image to enlarge
Readiness Dashboard
Review the effective catalog, safety flags, and the next validation steps before you publish WebMCP.
Click image to enlarge
Merged Catalog
See built-in and discovered capabilities together with risk, confidence, auth, and status.
Click image to enlarge
Publish and Export
Tier preview, diagnostics, and generated WebMCP output from one merged catalog.
Why this matters
Agent-readiness is a technical capability: agents can discover what your WordPress site intentionally exposes, and you can verify that contract end to end.
Controlled content visibility
Content, navigation, taxonomy, and product catalog data can be made legible 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 a clear contract, not broad exposure of every possible interaction.
Directory-ready infrastructure
Published sites can later opt into a reviewed directory of verified Open for Agents deployments.
Safety model
Read-only by default
Launch surfaces are designed around read-only discovery and validation. State-changing paths require explicit review and are not part of the default public story.
Publishing is explicit
Public agent-readable surfaces are opt-in. If publishing is disabled, public endpoints should not pretend to be available.
Release controls
Public endpoints stay closed until their storage, review, and privacy paths are configured.
Validation-first
Checks report what is present, missing, or blocked so operators can fix their setup before publishing.
Who it's for
Independent publishers
You run a content operation and want agents to read the public site through an explicit, validated contract.
Agencies
You manage multiple WordPress sites and need repeatable, explainable agent-readiness checks for client infrastructure.
WooCommerce operators
You care about product and catalog data becoming legible to agents without skipping safety review.
Developer-led organisations
You use WordPress inside a broader stack and want structured agent integration that can be tested like infrastructure.
Documentation
Getting Started
Install the plugin, review the default surfaces, validate the public contract, and publish deliberately.
Read guideAction Types
Definitions for action types, risk levels, confidence, and auth flags.
Open referencePublication Tiers
When to choose public minimal, standard, or private publishing tiers.
View tiersFAQ
Answers on Standard Tools, discovery scans, WooCommerce, compatibility, and data.
Read FAQBuilt by a WordPress Publisher
Open for Agents is built by Enoki Limited in New Zealand. We have been publishing on WordPress for 20 years. When AI agents started interacting with our sites in unpredictable ways, we built the tool we wished existed: specific, conservative, and testable.
Get Early Access
Open for Agents makes WordPress safely agent-readable. Subscribe for launch updates, host configuration guides, and directory availability.
Have questions? Reach us on X @openforagents or email hello@openforagents.com.
Prefer context first? See the Getting Started guide.