What Agent Adapt works with: WooCommerce setups, checkouts, hosts and other plugins Free & Pro

This page says what Agent Adapt is tested with, what it needs, and where it has not been tried. "Tested" means the plugin’s integration suite runs it on every release; "should work" means it relies only on standard WooCommerce behaviour but the suite doesn’t cover it; "not tested" means exactly that. We would rather say so than guess.

Versions

	Minimum	Tested with
WordPress	6.8	6.8 and the current release (the readme says up to 7.1)
WooCommerce	10.0	10.0 and the current release
PHP	8.1	8.1 and newer

Below a minimum, the plugin stays inactive and names the missing requirement in your dashboard. It never loads partway.

WooCommerce features

Feature	Status	Notes
Block cart and checkout	Tested	The customer’s browser checks out through the block checkout in the suite
Classic (shortcode) cart and checkout	Tested	Order attribution is recorded on both paths
High-performance order storage (HPOS)	Tested	Compatibility is declared; orders are read and written only through WooCommerce’s own order functions
Order attribution	Tested	Agent orders carry the agent as source, medium personal_agent
Coming soon / site visibility	Tested	The agent API works; an agent’s browser sees the coming-soon page like any visitor
Guest checkout	Should work	The checkout link adds items to the browser’s cart; whether the customer must sign in to pay is your checkout’s setting, as for any visitor
Catalogue visibility (hidden products)	Tested	Hidden products are never served to agents
Coupons	Tested	Applied by code; your usage rules apply
Variable products	Tested	Variations by ID, or by attributes for "any" attributes
Taxes, shipping, sale prices	Should work	The cart is a real WooCommerce cart, so your settings apply; the suite checks totals on a simple configuration
Multi-currency plugins	Not tested	Prices are reported in the store’s currency as WooCommerce’s Store API returns them

Hosting

Requirement	Why
HTTPS, on your own domain	The protocol is HTTPS-only. There is no "allow HTTP" switch, on purpose
WordPress at the root of the domain	Discovery is at /.well-known/poppy.json. A sub-folder install needs that one path forwarded
Pretty permalinks	The protocol’s endpoints are paths, not files
The Authorization header reaching PHP	Some hosts strip it; a one-line .htaccess rule fixes Apache, and Site Health gives it
/.well-known/, /agent-adapt/ and /wp-json/agent-adapt/ not cached or challenged	Caches and bot-fighting rules answer before WordPress otherwise

All five are checked by Tools → Site Health. Nginx hosts generally pass the Authorization header already; if yours does not, the host has to change its PHP configuration.

Setup	Status
Apache with .htaccess	Tested
Nginx	Should work; Site Health confirms the header
A CDN or proxy in front (Cloudflare and similar)	Should work with the path exclusions above; if the proxy hides your public address from WordPress, the agentadapt_public_origin filter sets it
Managed WordPress hosts	Should work; the ones that strip the Authorization header need a support ticket
Multisite	Not tested
A store in a sub-folder (example.com/shop/)	Works once the discovery path is forwarded; Site Health checks

Other plugins

Plugin type	Status
Page caches (WP Rocket, LiteSpeed Cache, W3 Total Cache and similar)	Should work with the three paths excluded. Agent responses are marked private, so a cache that respects headers never stores them anyway
Security and firewall plugins (Wordfence and similar)	Should work unless a rule blocks /wp-json/ or challenges non-browser clients; exclude the three paths
Product add-on plugins that need a form on the product page	Not supported through the agent API. An agent adds products with standard variations and quantities; add-on fields are not part of the API
WooCommerce Subscriptions, Bookings, returns and RMA plugins	No integration. Agents see the products and orders these plugins create as ordinary products and orders. Subscription changes and booking changes through agents are on the roadmap for Pro, not built
Translation plugins (WPML, Polylang)	Not tested. Product text is served as WooCommerce’s Store API returns it for the request’s language
Other agent or AI plugins	No conflict is known, and none is tested. Agent Adapt uses its own URL namespace and database tables

What Agent Adapt never touches

• WordPress’s and WooCommerce’s own REST APIs: agent tokens are refused there.
• Your checkout, payment gateways and order emails: an agent order is an ordinary order the customer paid for.
• Your theme: the consent, device and checkout-link pages are the plugin’s own small pages; everything else is your storefront.
• Customer passwords, card details or sessions on the website, until a customer opens a checkout link, which adds items to their cart.

Reporting what works for you

If you run Agent Adapt on a setup marked "should work" or "not tested" and it does or doesn’t, tell us at [email protected] with the plugin or host name and version. We update this page from reports, and we say which.

Common questions

Does it work on multisite?

It has not been tested on multisite. Nothing in it is multisite-specific, but discovery must answer at the root of each store’s domain, so a sub-directory network would need the path forwarded for each site.

Does it need the block checkout?

No. Both the block and the classic checkout are tested. The checkout link lands on whichever your store uses.

Will it slow my store down?

Agent requests are ordinary WordPress requests, within rate limits. The discovery documents are cacheable for five minutes. The only scheduled work is an hourly clean-up of short-lived records and the deletion of events older than 90 days.

Does it work without WooCommerce?

No. It needs WooCommerce 10.0 or newer, and until WooCommerce is active it does nothing except show a notice.