Does it work with multisite?

Subdomain multisite works: each subsite serves its own manifest. Subdirectory multisite also works for /ai2w and its routes (the request path is resolved against each site's home URL); the domain-root /.well-known/ anchor belongs to the network's main site, so subsites are discovered via /ai2w and the tag. /.well-known/ai2w returns a 404 on my server On Apache with the standard WordPress .htaccess, requests reach WordPress and the plugin serves the anchor. On some nginx setups a location ^~ /.well-known/ block serves that path directly and never reaches WordPress; add a rule to pass /.well-known/ai2w to WordPress, or serve it as a static pointer to /ai2w.

by Roland 0 (0 reviews)

AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents

Name: AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents
Author: Roland

Make your website AI-native. One open manifest plus REST and MCP endpoints so AI agents can discover, understand and safely act on your site.

AI2Web ranks #56,613 among WordPress.org plugins with 0+ active installations, is #10,707 of 12,493 in the E-commerce category, and was last updated Jul 24, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.6 (Current: 7.1.2)

v0.4.3 Current Version v0.4.3

Updated 1 month ago Last Update on 24 Jul, 2026

Refreshed 12 hours ago Last Refreshed on

#10,707 of 12,493 in E-commerce

View on WordPress.org

Rank

#56,613

— No change

Active Installs

— No change

KW Avg Position

163

3 worse

Downloads

211

+3 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 50%

0+ 10+

11,060

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 5 more installs to reach 10+

Rank Changes

Current #56,613

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 0.4.3
Last Updated: Jul 24, 2026
Requires WP: 6.0+
Tested Up To: 7.0.6
PHP Version: 8.0 or higher
Author: Roland

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Agents AI ChatGPT mcp woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,758

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)

Google for WooCommerce

800K+ installs

#75

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#81

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#116

View all Ecommerce plugins

Frequently Asked Questions

Common questions about AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents

No. The manifest and discovery endpoints expose only public metadata. Order tracking requires the correct billing email for that order, lookups are rate limited, and a wrong email is indistinguishable from a missing order, so nothing can be enumerated.

No. Refund and return actions only log a request as an order note for you to action in WooCommerce. Checkout creates a pending order and returns a secure payment link; the customer pays in the browser and the agent never handles payment details. No money moves without a human.

Enable the MCP endpoint on the settings page (on by default), then add https://your-site.com/ai2w/mcp as a custom connector / MCP server in the assistant. Your declared actions appear as tools.

Yes, if you enable ACP checkout (Settings -> AI2Web; it needs Agent checkout on). AI2Web implements the Agentic Commerce Protocol 2026-04-17 checkout sessions and a product feed, backed by a real WooCommerce cart, so a shopper's agent can assemble a cart, choose a variation, add a shipping address and coupon, and see live shipping and tax. To charge in-agent, provide a Stripe secret key (an AI2WEB_STRIPE_SECRET_KEY constant in wp-config.php, or the WooCommerce Stripe gateway): AI2Web then confirms a Stripe PaymentIntent from the Shared Payment Token the agent supplies. Without a key, completing a checkout creates a pending order and returns its secure payment link for the customer to pay in the browser. Either way the agent never handles card details.

Both let AI agents buy from your store; they are complementary and you can enable either or both. ACP (OpenAI/Stripe) is a session-based checkout that powers ChatGPT Instant Checkout - the agent drives a live cart and completes with a Shared Payment Token. AP2 (Google) is mandate-based: your store signs a Cart Mandate guaranteeing the price, and the buyer's agent settles it with a signed Payment Mandate. AI2Web implements the merchant side of both from the same WooCommerce catalogue.

They are alternative projections of the same manifest, for agents that read those formats. You do not maintain them separately; they are generated from /ai2w.

On WordPress 6.9+/7.0, the plugin registers its actions with the native Abilities API so WordPress's own AI Client and MCP Adapter can use them. This surface is authenticated (gated by WordPress permissions), separate from the public /ai2w surface.

No. WooCommerce 10.9+ ships its own canonical abilities (product and order query, create, update, etc.) into the same Abilities API. Those are merchant-facing and authenticated, for a store operator driving their shop from an AI client. AI2Web's actions are the opposite: customer-facing, anonymous, and ownership-gated (an external shopper's agent with no WordPress account), served from /ai2w/mcp and REST. To keep the native, authenticated surface tidy, AI2Web stops registering its read actions that WooCommerce now covers canonically (search_products, check_stock, track_order) as WordPress abilities when WooCommerce 10.9+ is active. They stay available on the public /ai2w surface, which WooCommerce's abilities do not serve.

No. The manifest, feeds and endpoints are useful today, and the MCP endpoint works with current assistant connectors without any AI key on your side.

Subdomain multisite works: each subsite serves its own manifest. Subdirectory multisite also works for /ai2w and its routes (the request path is resolved against each site's home URL); the domain-root /.well-known/ anchor belongs to the network's main site, so subsites are discovered via /ai2w and the <link rel="ai2w"> tag. /.well-known/ai2w returns a 404 on my server On Apache with the standard WordPress .htaccess, requests reach WordPress and the plugin serves the anchor. On some nginx setups a location ^~ /.well-known/ block serves that path directly and never reaches WordPress; add a rule to pass /.well-known/ai2w to WordPress, or serve it as a static pointer to /ai2w.