Documentation
FAQ
Where can I install the Core plugin?
Core 0.3.49 is available from the official WordPress.org plugin listing. The optional Open for Agents Assistant 0.1.11 is a separate add-on and is not included in the WordPress.org package.
Is the Assistant included with the Core plugin?
No. The Core plugin decides what agents may know and do. Open for Agents Assistant is a separate add-on that provides the on-site conversation interface. A separately hosted service connects the Assistant to the model. Installing Core does not install or activate either.
Can I download the Assistant add-on?
Not as a general public download. The Assistant add-on and managed service are currently limited to approved deployments and are not yet offered as a general public download or self-service subscription. The Assistant product page explains what the Assistant does and who can use it today.
Is there a live demo?
Yes. The Live WordPress Demo shows Open for Agents running on a hosted WordPress site. Start with the Storefront Assistant; the Buddy and Kitchen demos show creative breadth.
Do I need an API key?
Visitors do not need an API key for the official demo, and they should never paste a model credential into WordPress or a browser page. Model credentials remain server-side on the secure hosted service. A developer who self-hosts a compatible gateway must configure and protect their own server-side credentials.
What does the hosted service do?
The secure hosted service safely connects Open for Agents Assistant to the model and the site’s reviewed capabilities. It keeps model credentials server-side, restricts the accepted site origin and tool catalog, and carries the conversation through the existing approval and execution controls. Technical documentation may call this service a gateway.
Is the managed Assistant generally available?
No. The official demo is live today. The Assistant add-on and managed service are currently limited to approved deployments and are not yet offered as a general public download or self-service subscription.
Can I self-host the gateway?
A compatible self-hosted gateway is an advanced option for agencies and developers. They must operate the service, protect model credentials, enforce the exact origin and reviewed tool boundary, and maintain the security controls described in the Assistant documentation. It is not the normal setup for most site owners.
Can the Assistant place orders or take payments?
No. The current Assistant may search and compare products and can ask a visitor to approve a supported cart change. Checkout, payment, order placement, authentication, and account changes remain human-only.
How much does the Assistant cost?
Pricing has not been announced. The Assistant add-on and managed service are not available as a self-service subscription.
Does the plugin send Standard Tools or scan data to your servers?
No. Built-in catalog state, scan results, and published tool information stay on your WordPress site unless you explicitly export and share them. Scan and validation History is stored as private WordPress database records, is available only to authorized administrators, and is not part of the public agent catalog.
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.
Which form plugins are supported?
Contact Form 7 and WPForms Lite have tested detection, reviewed publication, and tested submission support for supported single-page forms. Execution is disabled by default and enabled one reviewed form at a time. See the Integrations matrix for exact versions and limitations.
Does enabling a form provider enable every form?
No. Form tools are registered per form ID. An administrator must review and opt in to each eligible form, and the visitor must see the exact values and approve before an irreversible submission. Forms with uploads, payment or checkout fields, account credentials, signatures, multi-page execution, calculations, or other unsupported capabilities are not made available.
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 Core 0.3.49 requires WordPress 6.4 or later and PHP 8.1 or later. It is tested through WordPress 7.1.
Does it work with my theme?
Standard Tools is designed to work independently of the active theme because it uses plugin-managed read-only REST routes. Site-specific discovery depends on the forms, structured markup, custom code, and supported integrations present on the site, so review the detected capabilities before publishing them.
What happens when the WebMCP spec changes?
The plugin keeps built-in and discovered capabilities in its own ActionMap model. WebMCP is live in Chrome's origin trial, but it remains experimental and pre-standard. A future WebMCP change may require a plugin update and fresh validation; keeping the reviewed ActionMap separate means the browser API is not the site's only record of its capabilities. Read why agent-ready websites matter now for a plain-language explanation of direct browser access, owner governance, and the optional Assistant.
Does llms.txt improve Google Search rankings?
No. llms.txt is an optional compatibility resource for agent clients that choose to read it. Google Search says it ignores the file for inclusion and ranking. Crawlable, useful visible content, indexing, and normal SEO foundations still matter. See the official Google Search guidance.
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 run a Broader Discovery 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 | The scan found more hooks or routes than it could safely process in one run. | Review the discovered actions. Do not publish them automatically. |
surface_mining_low_confidence | The scan found actions it could not identify with enough confidence. | Validate or disable those actions before publication. |
How do I uninstall the plugin?
Deactivate and delete it from WordPress like any plugin. Export the current action map first if you want to keep a record of the plugin's configuration. Uninstall also removes the plugin options and related database-backed History records from your WordPress install.
Does it support multisite?
No. The current version does not support WordPress multisite.