Head to head · Commerce orders · October 2026 research run

Fabric vs Wix Stores and eCommerce API

Wix Stores and eCommerce API scores 61.4 (C) on agent readiness against Fabric's 43.7 (E), and leads in 5 of 7 scored categories. Both do commerce orders.

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

Which one, for what

Fabric E

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Wix Stores and eCommerce API C

Best for An agent managing a merchant's existing Wix store or building a headless storefront on Wix.

Ahead on

  • Reliability, 48 against 23
  • Agent ergonomics, 68 against 57
  • Payments & pricing, 30 against 0
  • Maintenance & community, 83 against 15
  • Transparency & trust, 77 against 55

Watch for

No numeric rate limit for the REST API was found in the reviewed documentation. The 429 guidance is to wait a minute and retry

Score by category

CategoryWeight this runFabricWix Stores and eCommerce APIEdge
Reliability16%202348Wix Stores and eCommerce API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27976Fabric +3
Agent ergonomics13%16.25768Wix Stores and eCommerce API +11
Security & auth14%17.56261Fabric +1
Payments & pricing10%12.5030Wix Stores and eCommerce API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81583Wix Stores and eCommerce API +68
Transparency & trust7%8.85577Wix Stores and eCommerce API +22
Negative events≤1500
TotalE 43.7/100C 61.4/100

Facts side by side

FactFabricWix Stores and eCommerce API
KindHTTP APIHTTP API
VendorCommerce Fabric, Inc.Wix.com Ltd.
Hosted endpointhttps://api.fabric.inc/v3https://www.wixapis.com
TransportsHTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order formProprietary service under the Wix Terms of Use. @wix/sdk, @wix/stores and the wix/skills repository are MIT. @wix/mcp states no licence
Tools exposednone18
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.wix/mcp
Last releasenone2026-10-08
Terms last updated2026-01-01couldn't be read
Privacy policy last updated2021-01-14couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone87k npm/wk

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.

Wix Stores and eCommerce API

The developer docs are served as Markdown with an llms.txt index, and API keys carry permission scopes and a site restriction. No numeric REST rate limit or OpenAPI file was found, and status.wix.com records a platform-wide incident of 3 hours 17 minutes on 1 August 2026. A person must create the account and the key.

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

Wix Stores and eCommerce API

  1. Send the API key in Authorization with wix-site-id for site calls or wix-account-id for account calls, never both
  2. Fetch the product first and pass product.revision on every Catalogue V3 update, or the call fails with 409
  3. Use Cart V2 for new work. The older eCommerce Cart and Checkout APIs were deprecated on 5 August 2026
  4. Request cursorPaging.limit of at most 100 on Query Products and use Search Products for lookups by name
  5. Over MCP, read the method page with ReadFullDocsArticle before CallWixSiteAPI. Responses are cut at 50,000 characters by default

Questions

Which is better for AI agents, Fabric or Wix Stores and eCommerce API?

Wix Stores and eCommerce API scores 61.4 (C) on agent readiness against Fabric's 43.7 (E), and leads in 5 of 7 scored categories.

Do Fabric and Wix Stores and eCommerce API need an API key?

Fabric uses an OAuth sign-in. Wix Stores and eCommerce API takes an API key or an OAuth sign-in.

Can an agent call Fabric and Wix Stores and eCommerce API without installing anything?

Yes. Fabric has a hosted endpoint at https://api.fabric.inc/v3 and Wix Stores and eCommerce API at https://www.wixapis.com.

Other comparisons with Fabric or Wix Stores and eCommerce API

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.