Title: AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents
Author: Roland
Published: جولای 23, 2026
Last modified: جولای 23, 2026
---
Search plugins
# AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents
By [Roland](https://profiles.wordpress.org/rolandfarkas/)
[Download](https://downloads.wordpress.org/plugin/ai2web.0.4.3.zip)
* [Details](https://ps.wordpress.org/plugins/ai2web/#description)
* [Reviews](https://ps.wordpress.org/plugins/ai2web/#reviews)
* [Installation](https://ps.wordpress.org/plugins/ai2web/#installation)
* [Development](https://ps.wordpress.org/plugins/ai2web/#developers)
[Support](https://wordpress.org/support/plugin/ai2web/)
## Description
**Describe your website once. AI2Web makes it understandable to every AI.**
AI agents are starting to use the web, but the web was built for human eyes. Agents
scrape HTML, guess at forms, and render whole pages just to find one price or one
button. AI2Web fixes that by publishing a single, structured description of what
your site can do, and serving backend-first endpoints agents can call directly.
No scraping, no per-vendor rebuild.
AI2Web is a vendor-neutral capability layer. It sits _above_ protocols like MCP
and ACP and speaks whichever one an assistant understands, rather than competing
with them.
#### What it serves
On activation the plugin serves, from your own domain:
* `/.well-known/ai2w` – the discovery anchor agents look for
* `/ai2w` – your site’s AI2Web manifest: identity, capabilities, transports, declared
actions, events, governance
* `/ai2w/mcp` – a Model Context Protocol endpoint. Add it to Claude, ChatGPT, Grok
or any MCP client and your declared actions become tools the assistant can call
* `/ai2w/content`, `/ai2w/search`, `/ai2w/products`, `/ai2w/events` – live, structured
content and catalog
* `/ai2w/actions/*` – the secure action endpoints
* `/ai2w/negotiate` – capability negotiation (agree a capability set and transport)
* `/llms.txt` – a plain-text summary and links, projected from the same manifest
* `/.well-known/agent.json` – a generic agent-capability document, also projected
from the manifest
The last two mean agents that speak `llms.txt` or a generic `agent.json` can use
your site without understanding AI2Web first, while `/ai2w` stays the authoritative
source.
#### Agentic checkout (ACP)
With WooCommerce active, AI2Web can expose an **Agentic Commerce Protocol (ACP)
checkout** so a shopper’s AI agent (for example ChatGPT Instant Checkout) can buy
from your store. The agent drives a real WooCommerce cart through a checkout session
at `/ai2w/acp/checkout_sessions` – adding items and a chosen variation, setting
a shipping address, picking a delivery option, applying a coupon – and sees your
live WooCommerce pricing, shipping rates and tax as it goes. A product feed at `/
ai2w/acp/feed` lets agents ingest your catalogue. The same flow is available as
MCP tools, so any MCP client can run it.
Payment stays safe by design. Completing a session hands the store a delegated payment
token. AI2Web ships a **Stripe Shared Payment Token** handler: when a Stripe secret
key is available (set an `AI2WEB_STRIPE_SECRET_KEY` constant in wp-config.php, or
configure the WooCommerce Stripe gateway), it confirms a Stripe PaymentIntent for
the order total and the buyer is charged in-agent. With no key configured, completion
creates a pending order and returns that order’s own secure payment link for the
customer to pay in the browser. Either way the agent never handles card details,
and the whole payment step is filterable (`ai2web_acp_complete_payment`) if you
use a different processor. Turn ACP on under Settings -> AI2Web (it requires Agent
checkout).
#### AP2 (Agent Payments Protocol)
AI2Web can also expose a Google **AP2** merchant surface (opt-in). AP2 represents
a purchase as signed “mandates”: the store answers a buyer agent’s Intent Mandate
with a merchant-signed **Cart Mandate** that guarantees the items and price for
a short window, then settles a user-signed Payment Mandate into a WooCommerce order.
It is served at `/ai2w/ap2` as a REST binding and a minimal A2A JSON-RPC endpoint,
with an agent card and a JWKS that publishes the cart-signing public key so any
party can verify the merchant’s signature. Enable it under Settings -> AI2Web (it
generates an RSA signing key on first use).
#### WooCommerce
When WooCommerce is active, AI2Web exposes safe commerce actions:
* **search_products** – search the catalogue by keyword
* **check_stock** – availability, price and stock by SKU or id
* **track_order** – order status, verified by the billing email on the order
* **check_return_status** – whether a return or refund request already exists
* **start_return** / **request_refund** – request only. They log the request as
an order note for you to action in WooCommerce and never issue a refund or move
money automatically. Approval-gated.
* **start_checkout** – an agent assembles a cart and the plugin creates a _pending_
order, returning WooCommerce’s own secure payment link for the customer to pay
in the browser. The agent never handles payment details, and no money moves until
the customer pays.
#### Contact forms
If Contact Form 7, Gravity Forms, WPForms, Fluent Forms or Elementor Forms is active,
AI2Web exposes a single approval-gated **submit_contact** action. On confirmation
the enquiry is emailed to your support address (never an arbitrary recipient, so
it is not an open relay) and is rate limited per IP.
#### WordPress 7.0 AI: Abilities API
On WordPress 6.9+/7.0, AI2Web also registers its actions as native **WordPress Abilities**,
with AI annotations (read vs. write, destructive). This exposes the same ownership-
verified, approval-gated actions to WordPress’s own AI Client and MCP Adapter, so
a connected assistant can use them through WordPress too. Two surfaces, one definition:
* `/ai2w` – the public, anonymous, open-protocol surface (ownership and approval
gated).
* WordPress Abilities – the authenticated WordPress-native surface, gated by WordPress’s
own auth.
#### Agent service
If you connect an AI provider in WordPress 7.0’s Connectors hub, AI2Web exposes `/
ai2w/agent`, a natural-language endpoint answered by WordPress’s built-in AI Client
using your provider. The plugin never handles an AI key.
#### OAuth2 (PKCE)
Agents can authenticate via an OAuth2 authorization-code + PKCE flow, where a logged-
in user approves access on a consent screen. Codes are single-use and short-lived,
tokens are stored hashed, PKCE uses S256, and the flow is served over HTTPS. Anonymous,
ownership-gated access remains the fallback, so a token is never required. OAuth
is a security-sensitive feature; review it for your threat model before relying
on it, and it can be turned off on the settings page.
#### AI Readiness Score
A settings page (Settings -> AI2Web) shows a live **AI Readiness Score out of 100**
and a compliance tier, lets you toggle each feature (MCP, agent service, OAuth2,
WooCommerce actions, returns/refunds, agent checkout, ACP, AP2), and set a public
support email.
#### Agent Sales dashboard
A separate **Agent Sales** screen (Settings -> AI2Web Agent Sales) tracks what AI
agents actually do on your store, computed entirely from local data – no external
service and nothing to set up. It attributes every order an agent created (through
agent checkout, ACP or AP2) and shows agent-driven revenue, order count, average
order value and pending value for a period you choose, broken down by protocol,
with a recent-orders table. It also surfaces engagement from the AI2Web events table:
discovery hits, queries, action calls, and query “misses” – searches an agent ran
that returned nothing, i.e. demand you are not yet meeting, which a read-only crawl
of your site could never reveal.
#### Safe by design
The most important part is what an agent _cannot_ do without asking. See the security
section below.
AI2Web is backend-first and API-driven. It does not scrape your frontend or rely
on browser tools.
### How it works
1. **Discovery.** An agent fetches `/.well-known/ai2w`, which points to `/ai2w`. Reading
the manifest never changes anything.
2. **Understanding.** The manifest declares your identity, capabilities, transports,
and each action’s input schema, risk level and whether it needs approval.
3. **Negotiation.** The agent can `POST /ai2w/negotiate` to agree a capability set
and a transport (REST or MCP).
4. **Acting.** The agent calls an action over REST (`/ai2w/actions/{name}`) or as
an MCP tool. Requests are validated against the declared schema. Sensitive actions
return a preview and require explicit confirmation.
Everything is generated from your live site and detected integrations, and the manifest
is filterable so themes and plugins can extend it.
### Privacy and security
* Discovery and the manifest expose only public metadata. Your admin email is never
published; a support contact appears only if you set one.
* **Ownership before private data.** Order actions never trust an order number
alone. The caller must also provide the billing email, and it must match the
order. A wrong email and a nonexistent order return the identical “not found”
response, so agents cannot enumerate which orders exist.
* **Approval before money or commitment.** Refunds, returns, checkout and contact
enquiries return a preview first and only proceed on explicit confirmation.
* **Request only for money.** Refund and return actions add an order note for you
to review and never call WooCommerce’s refund process. Checkout creates a _pending_
order and hands the customer a payment link; the agent never handles payment.
* **Rate limited.** Order lookups, checkout and enquiries are throttled per IP.
* The WordPress Abilities surface requires an authenticated WordPress user; it
is gated by WordPress’s own permissions.
* **OAuth2 (PKCE)** is served over HTTPS, uses S256, issues single-use short-lived
codes, stores tokens hashed, and only issues them after a logged-in user approves
on a consent screen. A bearer token authenticates a request but does not elevate
its WordPress capabilities.
### External services
This plugin does not send any data to an external service by default. One optional
feature relies on a third party:
**Stripe** (agent-completed payments)
When, and only when, you (a) enable ACP checkout, (b) enter your own Stripe secret
key in Settings -> AI2Web, and (c) a shopper’s agent completes an order using a
delegated Stripe payment token, the plugin sends a single request to the Stripe
API (`https://api.stripe.com/v1/payment_intents`) to charge that order. If you do
not enter a Stripe key, no request is ever made and no data leaves your site.
Data sent to Stripe with that request: the order amount and currency, an order description,
the delegated payment token supplied by the agent, the order ID and checkout-session
ID, and (if present) the customer’s billing email as the receipt address. It is
sent over HTTPS at the moment the agent completes payment. No data is sent at any
other time.
Stripe is a service provided by Stripe, Inc. Please review their terms and privacy
policy:
* Terms: https://stripe.com/legal/ssa
* Privacy policy: https://stripe.com/privacy
## Screenshots
[⌊The AI2Web settings page: a live AI Readiness Score and compliance tier, with
links to your discovery manifest and MCP endpoint.⌉⌊The AI2Web settings page: a
live AI Readiness Score and compliance tier, with links to your discovery manifest
and MCP endpoint.⌉[
The AI2Web settings page: a live AI Readiness Score and compliance tier, with links
to your discovery manifest and MCP endpoint.
[⌊Feature toggles: MCP, the agent service, OAuth2 (PKCE), WooCommerce actions, agent
checkout, and the ACP and AP2 agentic-commerce surfaces.⌉⌊Feature toggles: MCP,
the agent service, OAuth2 (PKCE), WooCommerce actions, agent checkout, and the ACP
and AP2 agentic-commerce surfaces.⌉[
Feature toggles: MCP, the agent service, OAuth2 (PKCE), WooCommerce actions, agent
checkout, and the ACP and AP2 agentic-commerce surfaces.
[⌊The Agent Sales dashboard: agent-driven revenue, orders by protocol (agent checkout,
ACP, AP2) and engagement, computed entirely from local data.⌉⌊The Agent Sales dashboard:
agent-driven revenue, orders by protocol (agent checkout, ACP, AP2) and engagement,
computed entirely from local data.⌉[
The Agent Sales dashboard: agent-driven revenue, orders by protocol (agent checkout,
ACP, AP2) and engagement, computed entirely from local data.
## Installation
1. Upload the `ai2web` folder to `/wp-content/plugins/`, or install the zip from Plugins-
> Add New -> Upload.
2. Activate the plugin.
3. Make sure Permalinks are not set to “Plain” (Settings -> Permalinks).
4. Visit Settings -> AI2Web to see your AI Readiness Score and toggle features.
5. Visit `https://your-site.com/ai2w` to see your manifest.
6. To let an assistant use your site, add `https://your-site.com/ai2w/mcp` as a custom
MCP connector.
## FAQ
### Does this expose private customer data?
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.
### Can an AI issue a refund or take payment on my store?
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.
### How do I connect this to Claude, ChatGPT or Grok?
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.
### Can a shopper check out through an AI agent (ACP / ChatGPT Instant Checkout)?
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.
### What is the difference between ACP and AP2?
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.
### What is /llms.txt and /.well-known/agent.json?
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`.
### What are the WordPress Abilities it registers?
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.
### Does it clash with WooCommerce 10.9’s own agent abilities?
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.
### Do I need OpenAI/Anthropic to use AI2Web?
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.
### 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`.
### How do I authenticate an agent (OAuth2)?
Enable OAuth2 (PKCE) on the settings page. An agent sends the user to `/ai2w/oauth/
authorize`, the user approves on a consent screen, and the agent exchanges the code
for a token at `/ai2w/oauth/token` (PKCE S256). The token is then sent as an `Authorization:
Bearer` header. Anonymous, ownership-gated access still works without a token.
### How do I customise the manifest?
Use the `ai2web_manifest` filter, or the targeted `ai2web_support_contact`, `ai2web_governance`,`
ai2web_usage_policy`, `ai2web_legal`, `ai2web_knowledge`, `ai2web_oauth_allowed_clients`
and `ai2web_oauth_allow_insecure` filters.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents” is open source software. The following
people have contributed to this plugin.
Contributors
* [ Roland ](https://profiles.wordpress.org/rolandfarkas/)
[Translate “AI2Web – MCP, ACP, AP2 & NLWeb for AI Agents” into your language.](https://translate.wordpress.org/projects/wp-plugins/ai2web)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/ai2web/), check out
the [SVN repository](https://plugins.svn.wordpress.org/ai2web/), or subscribe to
the [development log](https://plugins.trac.wordpress.org/log/ai2web/) by [RSS](https://plugins.trac.wordpress.org/log/ai2web/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 0.4.3
* **OAuth Protected Resource (RFC 9728)**: new `/.well-known/oauth-protected-resource`
document telling agents (and MCP clients) which authorization server guards the
AI2Web endpoints. Served only when OAuth2 is enabled.
* **Content Signals + robots.txt projection**: the `usage_policy` you already declare
in the manifest is now projected into robots.txt as a `Content-Signal` directive
and sent as a `Content-Signal` response header, so crawlers can actually read
your stated preferences. Additive only – your existing robots.txt rules are never
modified – and filterable via `ai2web_project_robots_txt`.
* **Discovery `Link` header**: every front-end response advertises the manifest
via `Link: <.../ai2w>; rel="ai2w"` (RFC 8288), so non-HTML clients discover it
without parsing a page. Filterable via `ai2web_send_discovery_headers`.
* **Markdown for agents**: `/ai2w/content` returns Markdown when the request sends`
Accept: text/markdown` (with `Vary: accept`); JSON remains the default.
#### 0.4.2
* **Compatibility**: the plugin no longer relies on `array_is_list()`, so it runs
on its declared minimums (PHP 8.0, WordPress 6.0) rather than needing PHP 8.1/
WordPress 6.5.
* The optional **WordPress 6.9 Abilities API** and **WordPress 7.0 AI Client**
integrations are now explicitly guarded, so they are never called on cores that
do not provide them.
* Housekeeping: added a `License URI` header, escaped an admin readiness glyph,
trimmed an over-long upgrade notice, and documented the OAuth redirect and table-
name query annotations.
* No configuration changes; nothing to do after updating.
#### 0.4.1
* New **NLWeb (nlweb.ai) endpoint**: exposes `/ai2w/nlweb/ask`, an NLWeb-compatible
natural-language query over your posts, pages and WooCommerce products, returning
schema.org-style results. Agents that speak NLWeb can now search your site through
AI2Web, and the surface is advertised in the manifest under `transports.nlweb`(
plus a `conversational` capability). It is a keyword projection over WordPress
search, not NLWeb’s own semantic engine. Toggle under Settings -> AI2Web.
#### 0.4.0
* New **Agent Sales dashboard** (Settings -> AI2Web Agent Sales): see what AI agents
are doing on your store, computed entirely from local data. Shows agent-driven
revenue, order count, average order value and pending value over a selectable
window, a breakdown by protocol (agent checkout / ACP / AP2), a recent agent-
orders table, and engagement from the local events table (discovery hits, queries,
query “misses” that reveal unmet demand, and action calls). Nothing is sent to
any external service.
* New **ACP (Agentic Commerce Protocol) checkout** (spec 2026-04-17): a customer-
facing agentic checkout so a shopper’s agent (for example ChatGPT Instant Checkout)
can run a full cart -> shipping -> coupon -> pay flow against a real WooCommerce
cart. Adds checkout sessions at `/ai2w/acp/checkout_sessions` (create, retrieve,
update, complete, cancel), a product feed at `/ai2w/acp/feed`, and the five matching
MCP tools (create/get/update/complete/cancel_checkout_session). Live WooCommerce
pricing, shipping rates, coupons and tax are projected as ACP totals in minor
units. Includes a **Stripe Shared Payment Token handler**: when a Stripe secret
key is available (an `AI2WEB_STRIPE_SECRET_KEY` constant or the WooCommerce Stripe
gateway), completing a checkout charges the buyer in-agent by confirming a Stripe
PaymentIntent; with no key it degrades safely to a pending order plus that order’s
secure pay link, so the agent never handles card data. Toggle under Settings -
> AI2Web (requires Agent checkout).
* New **AP2 (Agent Payments Protocol, Google) merchant surface** (v0.2.0, opt-in):
the store answers a buyer agent’s Intent Mandate with a merchant-signed **Cart
Mandate** (a W3C PaymentRequest guaranteeing items and price), and settles a
user-signed Payment Mandate into a WooCommerce order. Exposed at `/ai2w/ap2`
as both a REST binding (`/cart`, `/payment`) and an A2A JSON-RPC `message/send`
endpoint that returns proper A2A Task artifacts, with an agent card discoverable
at both `/ai2w/ap2/agent-card` and `/.well-known/agent-card.json` (advertising
the AP2 extension) and a JWKS (`/ai2w/ap2/jwks`) publishing the cart-signing
key. Carts support multiple items and quantities. Carts are signed as RS256 JWTs(
an RSA key is generated on first use, or supplied via an `AI2WEB_AP2_PRIVATE_KEY`
constant). Settlement runs through the `ai2web_ap2_settle_payment` filter, falling
back to a pending order + pay link. Enable under Settings -> AI2Web.
* **Richer product data**: product and variation detail for agents. `check_stock`
and the catalogue now report product type, attributes (size/colour/etc.), and,
for variable products, each purchasable variation with its own id, SKU, price,
selecting attributes and stock, plus the price range. `start_checkout` accepts
a `variation_id` (to buy a specific variant) and an optional `coupon` code.
* New **analytics** (RFC-0016 parity with the reference server): personal-data-
free, server-side interaction events stored in a local plugin table and fired
as an `ai2web_event` action so operators can forward them anywhere. Records discovery,
query, and action events, including query “misses” (the demand signal a read-
only crawl cannot produce). Filters are sanitised to non-identifying scalars,
the agent identity is coarse (User-Agent only, never an end-user), rows auto-
prune after 90 days, and the whole thing is filterable off via `ai2web_analytics_enabled`.
* **WooCommerce 10.9+ interop**: WooCommerce 10.9 ships its own canonical product/
order abilities into WordPress’s Abilities API and MCP Adapter. To avoid listing
near-duplicates next to them on that authenticated, merchant-facing surface,
AI2Web no longer registers its `search_products`, `check_stock`, or `track_order`
reads as WordPress abilities when WooCommerce 10.9+ is active (WooCommerce’s `
products-query` / `orders-query` cover them). Every AI2Web action, including
those three, remains fully available on the anonymous, ownership-gated `/ai2w/
mcp` and REST surfaces, which WooCommerce’s abilities do not provide. Filterable
via `ai2web_abilities_superseded_by_woocommerce`.
* **Hardened OAuth2 server**: least-privilege bearer authentication, so a token
authenticates a request without elevating its WordPress capabilities.
* **Strict PKCE and scope validation** on the authorize endpoint: the `code_challenge`
and requested scopes are validated up front and rejected if malformed.
#### 0.3.0
* Manifest upgraded to AI2Web protocol v0.2 (additive, backward compatible): governance(
rate limits and consent mode), a protective usage policy, opt-in legal fields,
and knowledge sources. All filterable.
* New **agent service** at `/ai2w/agent`, answered by WordPress 7.0’s built-in
AI Client using your connected provider (no AI key handled by the plugin).
* New **OAuth2 (PKCE)** authenticated access: authorization-code + PKCE (S256)
flow with a consent screen, single-use codes, hashed tokens and HTTPS enforcement.
Anonymous, ownership-gated access remains the fallback.
* New **agent checkout**: agents can assemble a cart into a pending order and receive
a secure payment link. The customer pays in the browser; the agent never handles
payment.
* New multi-surface projections: serves `/llms.txt` and `/.well-known/agent.json`
from the same manifest.
* WordPress 7.0 **Abilities API** integration: registers the actions as native
WordPress abilities (with AI annotations) so the built-in AI Client and MCP Adapter
can use them.
* Added a `` discovery tag and a subdirectory / subdirectory-multisite
path fix.
* Admin now surfaces detected contact-form plugins.
#### 0.2.0
* WooCommerce actions: product search, stock check, order tracking (billing-email
verified), and return/refund requests (logged for the merchant, never auto-processed).
* MCP endpoint at `/ai2w/mcp` exposing declared actions as tools for Claude / ChatGPT
connectors.
* Admin settings page with a live AI Readiness Score, feature toggles and a support-
email field.
* Contact action delivers approved enquiries to your support address (rate limited).
* Per-IP rate limiting on order lookups and enquiries.
#### 0.1.0
* Initial draft: manifest, discovery, content/search/products/events, WooCommerce
+ form detection, negotiation.
## Meta
* Version **0.4.3**
* Last updated **21 ساعتونه ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.0.2**
* PHP version ** 8.0 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/ai2web/)
* Tags
* [Agents](https://ps.wordpress.org/plugins/tags/agents/)[AI](https://ps.wordpress.org/plugins/tags/ai/)
[ChatGPT](https://ps.wordpress.org/plugins/tags/chatgpt/)[mcp](https://ps.wordpress.org/plugins/tags/mcp/)
[woocommerce](https://ps.wordpress.org/plugins/tags/woocommerce/)
* [Advanced View](https://ps.wordpress.org/plugins/ai2web/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/ai2web/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/ai2web/reviews/)
## Contributors
* [ Roland ](https://profiles.wordpress.org/rolandfarkas/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/ai2web/)