Agents work better with explicit tools than UI guessing
Site info, navigation, content lookup, and catalog browsing become safer and more reliable when agents get structured, read-only tools instead of scraping the UI.
Standard Tools First
Start with built-in, deterministic, read-only WordPress capabilities through Standard Tools, then scan later for forms, AJAX routes, WooCommerce flows, and other site-specific actions. Review, validate, and publish only what you want agents to use.
Join the early access list to start with a safe baseline first, then add deeper discovery scans when you need them.
Built-in read-only baseline. No scan required to get started.
We respect your privacy. See our privacy policy.
Site info, navigation, content lookup, and catalog browsing become safer and more reliable when agents get structured, read-only tools instead of scraping the UI.
Most WordPress sites need a deterministic starting point before deeper discovery. Standard Tools gives you that safe baseline immediately.
The goal is not exposing everything. It is turning on useful capabilities first, then publishing only the surfaces that fit your policy.
Turn on built-in, deterministic, read-only WordPress capabilities for site info, navigation, content browsing, content lookup, taxonomy lookup, and WooCommerce catalog reads when WooCommerce is active.
Use scans as the enrichment layer for forms, AJAX routes, plugin-specific flows, selectors, and richer browser runtime bindings when you want site-specific actions.
1
Add Open for Agents to your WordPress site like any other plugin, then enable Standard Tools to generate a built-in read-only baseline instantly.
2
Review site info, navigation, posts, taxonomy, and optional WooCommerce catalog reads in the same catalog you will later use for discovered capabilities.
3
Run diagnostics, preview runtime behavior, and confirm what is safe to expose. Standard Tools can be validated before any scan runs.
4
Choose a publication tier, keep sensitive or high-variance paths private, and publish only the capabilities you approve.
5
Give agents a safe baseline immediately, then run discovery scans later for forms, AJAX routes, plugin flows, and richer site-specific bindings.
Click image to enlarge
Review the effective catalog, safety flags, and the next validation steps before you publish WebMCP.
Click image to enlarge
See built-in and discovered capabilities together with risk, confidence, auth, and status.
Click image to enlarge
Tier preview, diagnostics, and generated WebMCP output from one merged catalog.
Standard capabilities are built-in and deterministic. Discovery scans add richer site-specific surfaces when you want them. Review, validation, and publication work against the same effective catalog.
Standard Tools gives you immediate access to stable read-only WordPress capabilities for site info, post types, navigation, posts, search, single-post lookup, term lookup, and optional WooCommerce catalog reads.
Scans enrich the catalog with forms, AJAX routes, plugin-specific flows, selectors, and browser runtime bindings that are unique to your site.
Built-in and discovered capabilities are reviewed together, validated together, and filtered through the same publication controls.
The baseline is read-only, publishing is opt-in, publication tiers stay conservative, and higher-risk surfaces remain under explicit review.
No. Enable Standard Tools and you immediately get a safe built-in baseline of read-only capabilities without crawling the site first.
Forms, AJAX routes, plugin-specific flows, selectors, richer runtime bindings, and other site-specific capabilities that are not part of the built-in baseline.
Yes. Standard Tools can be reviewed, validated, and published from the merged catalog before any scan runs.
WooCommerce automatically adds built-in read-only product search, product lookup, and product category tools when it is active, before you ever run a scan.
No. ActionMap is the plugin's internal model, supports private tiers, and can remain internal. Publishing WebMCP does not change that, so review, validation, and export workflows stand on their own.
Safe tiers are conservative by default, and sensitive capabilities remain private unless you intentionally expose them. Keep your normal bot controls in place for non-approved traffic.
You want to turn on a safe agent baseline without exposing sensitive parts of your site.
You care about discoverability and clean journeys. Open for Agents lets you publish a safe baseline first, then layer in deeper discovery where it improves the user path.
You maintain one or many sites and want repeatable baseline rollouts, clearer capability catalogs, and optional deeper scans before publishing decisions.
Install the plugin, enable Standard Tools, validate your baseline, and scan later if you want deeper discovery.
Read guideDefinitions for action types, risk levels, confidence, and auth flags.
Open referenceWhen to choose public minimal, standard, or private publishing tiers.
View tiersAnswers on Standard Tools, discovery scans, WooCommerce, compatibility, and data.
Read FAQOpen 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 and costly ways, we built the tool we wished existed.
Open for Agents gives WordPress sites a safe built-in agent baseline in one click, with optional deeper scanning for site-specific actions.
Have questions? Reach us on X @openforagents or email hello@openforagents.com.
Prefer context first? See the Getting Started guide.