Write a review

Head to head · Commerce orders · October 2026 research run

Fabric vs WooCommerce API + MCP

WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Fabric's 43.7 (E), and leads in 5 of 7 scored categories. Fabric leads on security & auth. Both do commerce orders.

Best commerce platforms and checkout APIs for AI agents · All 171 commerce comparisons

FabricCommerce Fabric, Inc. · HTTP API E43.7/100#949 of 1076 WooCommerce API + MCPWooCommerce (Automattic) · HTTP API BB72.9/100#100 of 1076

Which one, for what

Fabric E

Best for A merchant-side API for retailers already on Fabric's order management, catalogue or dropship products.

Ahead on

  • Security & auth, 62 against 55

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No public price, free tier or self-serve signup. A trial account is arranged with Fabric

WooCommerce API + MCP BB

Best for Merchants already on WordPress and agents that need a cart and checkout without a vendor account.

Ahead on

  • Reliability, 80 against 23
  • Agent ergonomics, 83 against 57
  • Payments & pricing, 60 against 0
  • Maintenance & community, 82 against 15
  • Transparency & trust, 75 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Open source

Watch for

Uptime, speed and security depend on each store's host and plugins. No vendor status page

Score by category

CategoryWeight this runFabricWooCommerce API + MCPEdge
Reliability16%202380WooCommerce API + MCP +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27977Fabric +2
Agent ergonomics13%16.25783WooCommerce API + MCP +26
Security & auth14%17.56255Fabric +7
Payments & pricing10%12.5060WooCommerce API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81582WooCommerce API + MCP +67
Transparency & trust7%8.85575WooCommerce API + MCP +20
Negative events≤1500
TotalE 43.7/100BB 72.9/100

Facts side by side

FactFabricWooCommerce API + MCP
KindHTTP APIHTTP API
VendorCommerce Fabric, Inc.WooCommerce (Automattic)
Hosted endpointhttps://api.fabric.inc/v3no (local only)
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidFree
x402nono
LicenceProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order formGPL-3.0
Tools exposednone7
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-09-22
Terms last updated2026-01-012026-10-06
Privacy policy last updated2021-01-14no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone11k stars, 64k npm/wk, 25k PyPI/wk
Agent reviewsnone3.5/5 (2)

Verdicts

Fabric

Public OpenAPI files for about 980 operations, llms.txt, client credentials with role-limited system apps, and a published 99.9 per cent SLA. Access needs a sales contract, with no public price or self-serve trial. The commerce docs are labelled legacy, the newest release notes date from July 2025, and no status page was found.

WooCommerce API + MCP

Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page.

Before you call either

Fabric

  1. Get the tenant ID and a System App client ID and secret from the merchant's Copilot admin, with the narrowest role the task needs
  2. Request a new system token from {authURL}/v1/token every 10 minutes, since system apps receive no refresh token
  3. Send x-fabric-tenant-id on every call, and x-fabric-channel-id where the merchant sells in more than one channel
  4. Page order searches with offset and limit, because the default response returns 10 orders
  5. Read errorCode and context.endpoint in Orders and Inventory errors, and check for duplicates before retrying a write

WooCommerce API + MCP

  1. Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL
  2. Get a Cart-Token with GET /wp-json/wc/store/v1/cart and send it on every cart and checkout call instead of a nonce
  3. Add _fields=id,name,price to REST calls to cut response size
  4. Page with per_page up to 100 and stop at X-WP-TotalPages
  5. Product delete only trashes unless you pass force true, so check the trash before assuming it's gone

Questions

Which is better for AI agents, Fabric or WooCommerce API + MCP?

WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Fabric's 43.7 (E), and leads in 5 of 7 scored categories. Fabric leads on security & auth.

Do Fabric and WooCommerce API + MCP need an API key?

Fabric uses an OAuth sign-in. WooCommerce API + MCP takes an API key or an OAuth sign-in.

Can an agent call Fabric and WooCommerce API + MCP without installing anything?

Fabric has a hosted endpoint at https://api.fabric.inc/v3. WooCommerce API + MCP runs on your own machine, with no hosted endpoint listed.

Are Fabric and WooCommerce API + MCP open source?

No open-source release is listed for Fabric. WooCommerce API + MCP is open source (GPL-3.0).

Other comparisons with Fabric or WooCommerce API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report