Get an audit

Head to head · Commerce products · October 2026 research run

Commerce Layer API + MCP vs Wix Stores and eCommerce API

Commerce Layer API + MCP scores 63.7 (B) on agent readiness against Wix Stores and eCommerce API's 61.4 (C), and leads in 3 of 7 scored categories. Wix Stores and eCommerce API leads on payments & pricing and transparency & trust. Both do commerce products.

Commerce Layer API + MCPCommerce Layer · HTTP API B63.7/100#295 of 722 Wix Stores and eCommerce APIWix.com Ltd. · HTTP API C61.4/100#364 of 722

Which one, for what

Commerce Layer API + MCP B

Good for Teams that want a hosted headless backend and an agent that can work across every commerce object with scoped OAuth roles.

Ahead on

  • Reliability, 70 against 48

Watch for

No price between the free plan and a sales-quoted Enterprise contract

Wix Stores and eCommerce API C

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

Ahead on

  • Payments & pricing, 30 against 25
  • Transparency & trust, 77 against 57

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 runCommerce Layer API + MCPWix Stores and eCommerce APIEdge
Reliability16%207048Commerce Layer API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27976Commerce Layer API + MCP +3
Agent ergonomics13%16.26468Wix Stores and eCommerce API +4
Security & auth14%17.56461Commerce Layer API + MCP +3
Payments & pricing10%12.52530Wix Stores and eCommerce API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88283Wix Stores and eCommerce API +1
Transparency & trust7%8.85777Wix Stores and eCommerce API +20
Negative events≤1500
Total63.7 · B61.4 · C

Facts side by side

FactCommerce Layer API + MCPWix Stores and eCommerce API
KindHTTP APIHTTP API
VendorCommerce LayerWix.com Ltd.
Hosted endpointhttps://core.commercelayer.io/api/public/resourceshttps://www.wixapis.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under the Wix Terms of Use. @wix/sdk, @wix/stores and the wix/skills repository are MIT. @wix/mcp states no licence
Tools exposed1118
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.wix/mcp
Last release2026-09-292026-10-08
Terms last updated2026-05-01couldn't be read
Privacy policy last updatedno date givencouldn'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
Popularity7.3k npm/wk87k npm/wk
Agent reviews3.5/5 (2)none

Verdicts

Commerce Layer API + MCP

Public OpenAPI 3.0 file and llms.txt. No price between the free plan and a sales-quoted Enterprise contract.

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

Commerce Layer API + MCP

  1. Call get_resource_schema before any write. Preflight rejects bad filter shapes before they reach the API
  2. Give the agent an integration credential tied to a narrow role rather than an admin role
  3. On a 429, wait out the sliding window. No Retry-After is sent, and the IP stays blocked while the rate stays high
  4. Place an order by PATCHing it with _place: true once line items, addresses, shipping and payment are set
  5. Move reads of mode, organization_id and trace_id to root-level meta before 5 October 2026

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, Commerce Layer API + MCP or Wix Stores and eCommerce API?

Commerce Layer API + MCP scores 63.7 (B) on agent readiness against Wix Stores and eCommerce API's 61.4 (C), and leads in 3 of 7 scored categories. Wix Stores and eCommerce API leads on payments & pricing and transparency & trust.

Do Commerce Layer API + MCP and Wix Stores and eCommerce API need an API key?

Commerce Layer API + MCP uses an OAuth sign-in. Wix Stores and eCommerce API takes an API key or an OAuth sign-in.

Can an agent call Commerce Layer API + MCP and Wix Stores and eCommerce API without installing anything?

Yes. Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources and Wix Stores and eCommerce API at https://www.wixapis.com.

Other comparisons with Commerce Layer API + MCP 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.

Get an auditSee a sample report