RXed AI News

AI to the bone.
SCORE 8/10 10/10 criteria · Strong Assessed 2026-09-12 · ARI rubric v1.0

WooCommerce — can an agent use it?

Visit woocommerce.com
“Open-source ecommerce platform for WordPress, powering 4M+ stores and 31% of the top 1 million ecommerce sites.” — the vendor’s own words

WooCommerce is the most agent-ready e-commerce platform we have scored. An official MCP server in developer preview already exposes product and order management; the full REST API covers every core action; and because it is self-hosted, there are no platform-imposed rate limits or anti-bot terms. The gap is agent payment protocols — no ACP/AP2/MPP/x402 support yet.

Category
E-commerce platform
Agent protocol
Agent payment rails
None published
Site Scan
C (74/100) · crawl-level, 12/09
Tap or hover any criterion to see why it scored that.
FIND & RETRIEVE8.5/10Can an agent get correct information?

Machine-readable surface8.5/10

Yoast-generated llms.txt indexes pages, posts, products, and documentation with summaries. Comprehensive sitemap with 27 sub-sitemaps. JSON-LD (Organization, WebSite, BreadcrumbList). Clean server-rendered HTML (772 words without JS). No bot wall on public pages. robots.txt has no AI-specific blocks. No markdown negotiation or MCP server card, but those are bonus-tier signals. source

Information retrieval quality8/10

Pricing page publishes a detailed comparison table with exact figures: 0% revenue share, per-transaction processing fees for WooPayments (2.50–2.90% + 30¢), and side-by-side TCO breakdowns against Shopify/BigCommerce/Salesforce/Adobe/Wix. Extension prices listed ($29–$299/year). Hosting ranges stated ($25–$350/month). The pricing is transparent and current — no 'contact sales' gates. Missing Offer schema markup on the pricing page drops it from a 9. source

Documentation for machines9/10

Full REST API v3 reference with per-endpoint documentation for 15+ resource types (products, orders, customers, coupons, taxes, shipping, payment gateways, webhooks, reports, settings, system status). Authentication documented for three methods (HTTP Basic, OAuth 1.0a, Application Passwords). Separate developer blog with changelogs, advisories, and release notes updated weekly. Getting-started guides, extension development docs, and theme docs. GitHub-hosted open-source codebase for inspection. Only gap: rate limits are not documented (self-hosted, so they depend on the host). source

ACT & TRANSACT7.1/10Can an agent do the job?

Action coverage9.5/10

The REST API v3 covers virtually every core commerce action: full CRUD on products (including variations, attributes, categories, tags, reviews), orders (notes, refunds, status changes), customers, coupons, shipping zones/methods, tax rates/classes, payment gateways, webhooks, reports (sales, top sellers), settings, and system status. Batch operations available on most endpoints. The WooCommerce CLI provides an additional programmatic surface. The only gap vs UI is some admin-level WordPress settings outside the commerce domain. source

Agent protocol support7/10

Official first-party MCP server built into WooCommerce core (developer preview). Exposes product management (query/create/update/delete) and order management (query/update status/add notes) via the WordPress MCP Adapter at /wp-json/mcp/mcp-adapter-default-server. Authentication via WordPress Application Passwords. Listed on the WooCommerce developer docs. However: still in developer preview (APIs may change), and coverage is narrower than the full REST API — no shipping, coupons, customer, or webhook management via MCP yet. Multiple community-built MCP servers also exist (wppoland/woocommerce-mcp, techspawn/woocommerce-mcp-server). Not yet in the official MCP registry. source

Access & auth friction8.5/10

Three authentication methods, all self-serve: REST API consumer keys (generated instantly in WP admin with read/write/read-write scoping), HTTP Basic Auth over HTTPS, and OAuth 1.0a for HTTP. Application Authentication endpoint lets apps request user-generated keys via callback flow. WordPress Application Passwords for MCP. No enterprise gate, no manual approval, no partner programme required. Credentials available in minutes. The only friction is that the store owner must be a WordPress admin to generate keys. source

Agent payment capability1.5/10

No evidence of any agent payment protocol support (ACP, AP2, MPP, x402). WooCommerce processes payments via gateway plugins (Stripe, PayPal, WooPayments) but none of these expose programmatic agent-delegated checkout. An agent cannot autonomously pay for or check out products on a WooCommerce store without human interaction on the payment page. The REST API can create orders but cannot complete payment programmatically — the payment step requires the gateway's hosted flow. source

Cost & rate fairness9/10

WooCommerce core is free and open-source — no platform fees, no revenue share, no API call charges. Rate limits are not imposed by WooCommerce itself (they depend on the hosting provider). No agent-vs-human price discrimination. Extensions are $29–$299/year per add-on, but the core API and MCP server are included at no cost. Hosting costs ($25–$350/month) are market-rate WordPress hosting. This is the most cost-accessible e-commerce API surface available. source

TRUST & DURABILITY7.5/10Will it still work next quarter?

Permission & ToS stance8/10

WooCommerce is open-source (GPL v3) — automation is inherently permitted by the license. robots.txt allows all crawlers with no AI-specific blocks (partial restrictions only on admin paths and search). The Terms redirect to WordPress.com ToS, which govern the wordpress.com hosted service rather than self-hosted WooCommerce installations. Self-hosted WooCommerce has no platform-level bot restrictions — the store owner sets their own rules. No hostile enforcement history against agents or scrapers. source

Reliability & continuity7/10

The REST API has been stable across v1→v2→v3 over years with backward compatibility maintained. Developer blog publishes changelogs, advisories, and pre-release notes regularly (latest: 11.1.0 on 2026-09-03). Open-source codebase on GitHub enables community inspection of changes. However: no public status page exists (status.woocommerce.com does not resolve) — uptime depends entirely on the store's hosting provider. Self-hosted nature means WooCommerce itself doesn't control uptime. The MCP server is still in developer preview, which introduces potential breaking changes. source

Sources

Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.