by shan 0 (0 reviews)

SDX AI Readiness Toolkit for WooCommerce

Name: SDX AI Readiness Toolkit for WooCommerce
Author: shan

Make your WooCommerce store first-class compatible with AI shopping agents: UCP discovery, MCP tools, OAuth 2.0, ACP checkout, audit dashboard.

SDX AI Readiness Toolkit for WooCommerce ranks #73,295 among WordPress.org plugins with 0+ active installations, is #10,113 of 14,124 in the E-commerce category, and was last updated Aug 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v0.4.0 Current Version v0.4.0

Updated 2 months ago Last Update on 27 Aug, 2026

Refreshed 1 week ago Last Refreshed on

#10,113 of 14,124 in E-commerce

View on WordPress.org

Rank

#73,295

— No change

Active Installs

-100%

KW Avg Position

— No change

Downloads

361

+2 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

45,727

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 10 more installs to reach 10+

Rank Changes

Current #73,295

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.0
Last Updated: Aug 27, 2026
Requires WP: 7.0+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: shan

Support & Rating

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

Keywords

acp AI mcp ucp 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,757

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

#74

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#82

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#115

View all Ecommerce plugins

Frequently Asked Questions

Common questions about SDX AI Readiness Toolkit for WooCommerce

No. WooCommerce 10.7+ ships internal ACP infrastructure with the agentic_checkout feature flag (default off). Our Coexistence detector activates our endpoints only when the WC native flag is off, and defers (410 + Location header) when on.

No. WooCommerce 10.9+ registers seven canonical abilities of its own (woocommerce/products-query, orders-query and friends) through the WordPress MCP Adapter. Two near-identical tool sets in front of the same agent makes tool selection worse, so the "WP Abilities" setting defaults to auto: when WooCommerce's canonical abilities are present, this plugin does not register its overlapping set, and the dashboard's MCP-004 check tells you that happened. Set the mode to all (or filter agtc_mcp_abilities_mode) if you want both. The plugin's own OAuth MCP server at /wp-json/agtc/v1/mcp is unaffected either way.

Yes — the release is integration-tested against a live WordPress 7.1 + WooCommerce 11.0.1 install: the UCP profile, the catalog capabilities, the MCP server, OAuth registration and token exchange, the ACP purchase flow that creates a real order, and the readiness dashboard all pass there. WordPress 7.1 keeps PHP 7.4 as its minimum, so no PHP change is needed.

UCP 2026-08-25, date-versioned as the specification requires. The profile advertises only the capabilities this plugin actually serves — currently dev.ucp.shopping.catalog.search and dev.ucp.shopping.catalog.lookup — because a platform negotiates against that document, and an over-claimed capability fails later in a worse place. payment_handlers is published as an empty map until the UCP checkout capability ships. You can extend the document with the agtc_ucp_profile filter.

Nothing is deleted by default. Deactivating the plugin only withdraws its rewrite rules; your signing keys, registered OAuth clients and settings stay put, so reactivating restores the exact same store identity. Deleting the plugin also leaves that data alone unless you tick Delete all plugin data on uninstall on the dashboard first — that opt-in exists because the master secret encrypts stored client data, and removing it cannot be undone.

Yes: 60 requests per minute, counted per declared platform profile (falling back to the caller's IP address). Over the limit the endpoint answers 429 with a Retry-After header and a UCP rate_limited message, which platforms are expected to honour. Tune or disable it with the agtc_ucp_catalog_rate_limit filter — returning 0 turns throttling off.

No. The UCP catalog endpoints expose only data your storefront already shows publicly, so they are unauthenticated. They do require the UCP-Agent header the specification mandates, so a misconfigured caller gets a protocol-shaped error rather than silently reading your catalog; the agtc_ucp_require_agent_header filter can relax that. Order data always requires an OAuth token and is scoped to the agent's own orders.

Only for ACP payment_intent flow. Without Stripe, agents can still discover, browse, and create checkout sessions — they just can't authorize payment through ACP directly. There are two flow models to choose from, and most stores can start without Stripe entirely: Model A — Agent pays directly (ACP payment_intent): Requires Stripe. The ACP protocol uses Stripe's PaymentIntent under the hood, so you must define AGTC_STRIPE_SECRET_KEY in wp-config.php. The agent never sees the customer's card; payment is captured server-side at session completion. This is the fully autonomous flow. Model B — Agent creates order, customer pays later: Works with any WooCommerce payment gateway — PayPal, Square, Stripe via WooCommerce Payments, bank transfer, cash on delivery, anything you already have configured. The agent creates an ACP session, which the plugin converts into a standard pending WooCommerce order. The customer receives an order link and completes payment using whatever gateway your store already uses. Recommendation: Most stores should start with Model B (no Stripe required) and add Model A later if and when they want fully autonomous agent purchases without a human checkout step.

By default, public product data only (name, price, description, images). An agent can additionally read its own orders if it holds the read:orders scope — but only orders it created itself through the ACP checkout flow. Agents never see other agents' orders or orders placed by human customers through normal checkout.

Order access is scoped to ownership and safe by default: an agent (OAuth client) can only ever read orders it created itself via the ACP checkout flow. It can never read another agent's orders or orders placed by human customers through normal checkout. To read its own orders, an agent must request the read:orders scope at registration; dynamic client registration only ever grants read:products by default, so read:orders must always be requested explicitly. No server-side opt-in or wp-config.php constant is required.