Documentation
FAQ
Does the plugin send Standard Tools or scan data to your servers?
No. Built-in catalog state, scan results, and generated contracts stay on your WordPress infrastructure unless you explicitly export and share them.
Do I need to run a scan to get started?
No. You can enable Standard Tools and immediately get a safe built-in baseline of read-only capabilities. That includes get_site_info, list_post_types, get_navigation, list_posts, search_posts, get_post, and get_terms with no scan required.
What does scanning add?
Scanning adds forms, AJAX routes, plugin-specific flows, selectors, richer runtime bindings, and other site-specific capabilities that are not covered by the built-in baseline.
Can I validate and publish without scanning?
Yes. Standard Tools can be reviewed, validated, and published from the effective merged catalog before any scan runs.
What happens on WooCommerce sites?
When WooCommerce is active, the plugin automatically adds built-in read-only product search, product lookup, and product category tools through woo_search_products, woo_get_product, and woo_get_product_categories.
Does this publish capability data publicly by default?
No. Public publication is disabled by default and must be enabled by an administrator. While publishing is disabled, public endpoints return 404 by design.
What is the canonical API URL?
Canonical endpoints are under /wp-json/open-for-agents/v1/*. The /.well-known/* endpoints are aliases for agent discovery and compatibility.
Will this slow down my site?
Standard Tools uses plugin-managed read-only REST routes. Discovery scans run as background operational tasks through WordPress scheduling, are not executed during normal visitor page loads, and are capped per run to keep admin usage responsive.
What versions are supported?
Open for Agents requires WordPress 6.4 or later and PHP 8.1 or later. Current CI coverage is WordPress 6.4-6.6 on PHP 8.1-8.4.
Does it work with my theme?
Yes. Standard Tools is theme-agnostic because it uses plugin-managed read-only REST routes. Discovery scanning relies on form and action semantics plus plugin integrations rather than theme-specific templates.
What happens when the WebMCP spec changes?
The plugin keeps built-in and discovered capabilities in its own ActionMap model. When WebMCP changes, exporter updates are shipped without requiring you to re-scan or reconfigure from scratch.
Does it work with caching plugins?
Yes, in normal configurations. Standard Tools is not dependent on a crawl, so caching usually does not affect the baseline. If cached responses hide dynamic forms during discovery scanning, run scans from an authenticated admin session and clear cache before the full pass.
Common warnings and what to do
| Warning Code | What It Means | Recommended Action |
|---|---|---|
search_form_not_detected | No canonical WordPress search form was found. | Verify search markup and rerun a full scan. |
js_submit_uncertain | JS-heavy or nonce-gated form behavior could not be fully inferred. | Prefer native detector coverage or keep the action private. |
plugin_form_requires_detector | Plugin form was detected but generic inference may be incomplete. | Use plugin-native detectors and rerun scan before publishing. |
ajax_mining_capped / rest_mining_capped | Mined hook/route discoveries exceeded cap limits and were trimmed. | Review mined actions privately; treat as discovery hints, not auto-publish targets. |
surface_mining_low_confidence | Low-confidence mined surfaces were added to the internal map. | Manually validate or disable uncertain mined actions before publication. |
How do I uninstall the plugin?
Deactivate and delete it from WordPress like any plugin. If you are running a production policy, export your latest action map first for audit history. Uninstall also removes the plugin options and related snapshot data from your WordPress install.
Does it support multisite?
Not yet. Multisite support is deferred for the current version.