Head to head · Commerce products · October 2026 research run

Square vs Wix Stores and eCommerce API

Square scores 69.2 (B) on agent readiness against Wix Stores and eCommerce API's 61.4 (C), and leads in 5 of 7 scored categories. Wix Stores and eCommerce API leads on transparency & trust. Both do commerce products.

Which one, for what

Square B

Good for Agents working for a seller already on Square, on catalogue, inventory, orders, payment links and customers, online and in person.

Ahead on

  • Reliability, 58 against 48
  • Schema & documentation, 87 against 76
  • Agent ergonomics, 83 against 68
  • Security & auth, 67 against 61
  • Payments & pricing, 40 against 30

Also in its favour

  • Runs on your own machine

Watch for

The MCP server is marked beta, and the remote server reaches production data only

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

  • Transparency & trust, 77 against 70

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 runSquareWix Stores and eCommerce APIEdge
Reliability16%205848Square +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28776Square +11
Agent ergonomics13%16.28368Square +15
Security & auth14%17.56761Square +6
Payments & pricing10%12.54030Square +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88183Wix Stores and eCommerce API +2
Transparency & trust7%8.87077Wix Stores and eCommerce API +7
Negative events≤1500
Total69.2 · B61.4 · C

Facts side by side

FactSquareWix Stores and eCommerce API
KindHTTP APIHTTP API
VendorBlock, Inc.Wix.com Ltd.
Hosted endpointhttps://mcp.squareup.com/mcphttps://www.wixapis.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceProprietary service under the Square Developer Terms of Service. The MCP server and the OpenAPI specification on GitHub are Apache 2.0, and the Node.js SDK is MITProprietary service under the Wix Terms of Use. @wix/sdk, @wix/stores and the wix/skills repository are MIT. @wix/mcp states no licence
Tools exposed318
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.wix/mcp
Last release2026-09-162026-10-08
Terms last updated2026-09-10couldn't be read
Privacy policy last updated2026-09-15couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn'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 waiveryescouldn't be read
Popularity454k npm/wk, 72k PyPI/wk87k npm/wk

Verdicts

Square

The REST API has a public OpenAPI 3.0 spec, OAuth scopes split by read and write for each resource, idempotency keys on writes and a free sandbox. The MCP server is in beta and its remote instance reaches production only. No numeric REST rate limits or SLA were found, and the status page recorded widespread errors on 27 September 2026.

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

Square

  1. Test against the sandbox first with the local MCP server and SANDBOX=true. The remote server at mcp.squareup.com reaches production only
  2. Set DISALLOW_WRITES=true on the local MCP server when the task only reads
  3. Call get_service_info, then get_type_info, before each make_api_request. The request body is otherwise untyped
  4. Send a fresh idempotency_key on every write, and reuse it when retrying the same write
  5. Pin Square-Version in each request. Use a page cursor within 5 minutes of receiving it

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, Square or Wix Stores and eCommerce API?

Square scores 69.2 (B) on agent readiness against Wix Stores and eCommerce API's 61.4 (C), and leads in 5 of 7 scored categories. Wix Stores and eCommerce API leads on transparency & trust.

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

Both take an API key or an OAuth sign-in.

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

Yes. Square has a hosted endpoint at https://mcp.squareup.com/mcp and Wix Stores and eCommerce API at https://www.wixapis.com.

Other comparisons with Square 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.