Head to head · Commerce catalogues · October 2026 research run

commercetools vs Square

commercetools and Square score within a point of each other on agent readiness, 70.7 (BB) and 69.9 (B). Square leads on payments & pricing. Both do commerce catalogues.

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

Which one, for what

commercetools BB

Best for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.

Ahead on

  • Reliability, 78 against 53
  • Maintenance & community, 85 against 71
  • Transparency & trust, 82 against 71

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No public price. The pricing page describes order-based pricing and sends buyers to sales

Square B

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

Ahead on

  • Payments & pricing, 60 against 30

Also in its favour

  • No incidents deducted, where commercetools loses 3 points for them

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Square +30

commercetools 30

No x402, MPP or L402 in the docs or pricing page (0). The pricing page describes order-based pricing with no figures and sends buyers to sales (0). A 60-day trial with every core commerce API, and the trial FAQ says no credit card or payment is needed (20). A person fills in a web form and follows an emailed link to create the account. API Clients can then be created through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Square 60

No x402, MPP or L402 found in the docs index or the spec (0). Fees are public without login. The API has no charge, and card payments through the payments APIs cost 2.9% + 30 cents in the US (20). The sandbox is free, and the Square Free plan is $0 a month (20). A person must create a Square account and an application in the Developer Console, or approve OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability commercetools +25

commercetools 78

Graded on the HTTP API with the hosted lines. status.commercetools.com lists seven components across five regions with a dated history (20). The history pages sit under /pages/, which the status site's robots.txt disallows, so they weren't re-read on 1 November. The 8 October check read the history and found only the API errors in Europe (Google Cloud) on 10 and 30 July, which have now left the 90-day window, and nothing on the API component from 3 August to 8 October. For 9 October to 1 November, the status page's own month metrics, read on 1 November, show 100.00 per cent uptime for the APIs in all five regions and every component operational. Those metrics rule out downtime on the API but don't list partial or degraded incidents, which this run counts as minor, so the 24 days since 8 October aren't shown to be clean. Minor at most (20 of 30, was 15, cause time). The HTTP API applies rate limiting only to non-production Projects since 16 October, with RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, but the docs say the limit varies and give no number, and production Projects have none. Numbers exist for query size (500 per page, offset 10,000), the Knowledge MCP (100 requests per 15 minutes per IP) and Managed MCP Servers (1,000,000 tool calls a project a month) (5). Retry guidance covers 429 (wait for Retry-After or RateLimit-Reset), 502 and 503 with exponential backoff, and 409 handling through resource versions. There are no idempotency keys (13). 99.9 per cent monthly availability with service credits of 10 to 50 per cent, though Managed MCP Servers are excluded (10). The API and Managed MCP Servers are not marked beta (10). 20 + 20 + 5 + 13 + 10 + 10 = 78.

Square 53

Graded on the hosted REST API. Status page at issquareup.com, now on incident.io with a page per country, whose United States page lists components including Developer Payments and Developer Sandbox (20). Its history starts in October 2026 and lists two partial incidents, Square Card wallet provisioning on 7 October and order sync to kitchen displays on 27 October, neither on the API. The 8 October reading of 15 incidents came from the old page's /api/ path, which robots.txt disallows, so it is struck, and August and September can't be read. No readable history for most of the window gives 5. No numeric limits were found for the REST API, and the docs say endpoints might enforce different limits. GraphQL is limited to 10 queries a second (5). The docs describe 429 RATE_LIMITED errors, exponential backoff with jitter and idempotency keys on writes (15). No SLA found in the developer terms or docs (0). The REST API is generally available, but 97 of 332 operations in the spec are beta and the MCP server is beta (8).

Maintenance & community commercetools +14

commercetools 85

Release notes dated 30 October 2026 (InStore), with API entries on 23 October (frozen Cart prices, Audit Log) and 22 October (Category Store assignments) (30). More than twenty dated entries between 8 and 30 October alone (20). Public release notes with RSS, and standard support with published first-response targets of 12 hours for problems and 48 hours for questions, per the 8 October check. GitHub issue handling wasn't read (12). Four official SDKs on a monthly schedule, with @commercetools/platform-sdk 9.7.0 tagged on 9 October 2026 (15). The Commerce MCP repository runs quality and release workflows with changesets, and its changelog adds 4.2.3 (a dependency update) on 23 October after six tagged releases between 3 August and 30 September 2026. Its server.json still names version 4.1.0 (8). 30 + 20 + 12 + 15 + 8 = 85.

Square 71

API version 2026-09-16 is the newest release, 46 days before the check, with no October release in the notes (20). Releases 2026-08-19 and 2026-09-16 in the last 90 days, with the Node.js SDK (45.1.0 on 18 August, 46.0.0 on 15 September) and Python SDK tagged for each (20). Public release notes, a developer forum and a Discord community are linked from the docs. GitHub issues were not readable, and the MCP server repository's only commits since April 2026 are README changes on 1 and 7 October (10). Seven official SDKs were regenerated for 2026-09-16, the Node.js one at 46.0.0. No Square server appears in the official MCP registry (15). The Node.js SDK has CI and integration workflows. The npm package square-mcp-server is still 0.1.2, tagged in April 2025 (6).

Transparency & trust commercetools +11

commercetools 82

Closed service under a public Master Service Agreement and a public 60-day trial agreement. The SDKs are MIT or Apache 2.0 and Commerce MCP is MIT (17). A privacy notice with a section for customers, a public DPA last updated 1 October 2024 and a sub-processor list. The DPA says personal data is deleted promptly at termination without a period in days, and the security page says the DPA is available on request while it is published at commercetools.com/dpa (22). Breaking changes are announced three months ahead and removals six months ahead in release notes, and a deprecations archive gives dates. The policy keeps a right to make larger changes with direct notice (16). Sub-processors listed with purpose, hosting location and product, updated 24 August 2026 (20).

Square 71

Closed service under published developer terms. The API spec and MCP server are Apache 2.0 and the Node.js SDK is MIT (15). The privacy notice was updated on 15 September 2026 and says retention is decided case by case, with no periods given. No public DPA was found at the addresses we tried (13). APIs are typically deprecated at least 12 months before retirement, retired endpoints return 410, and deprecated items are listed with dates (20). The privacy notice names categories of service providers and processing in the US, Japan, the UK and the EU. No named sub-processor list was found (8).

Score by category

CategoryWeightcommercetoolsSquareEdge
Reliability16%7853commercetools +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8687Square +1
Agent ergonomics13%8383even
Security & auth14%7067commercetools +3
Payments & pricing10%3060Square +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8571commercetools +14
Transparency & trust7%8271commercetools +11
Negative events≤15-30
TotalBB 70.7/100B 69.9/100

Facts side by side

FactcommercetoolsSquare
KindHTTP APIHTTP API
Vendorcommercetools GmbHBlock, Inc.
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}https://mcp.squareup.com/mcp
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MITProprietary 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 MIT
Tools exposednone3
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-09-16
Terms last updatedno date given2026-09-10
Privacy policy last updatedno date given2026-09-15
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity221k npm/wk454k npm/wk, 72k PyPI/wk
Agent reviews3/5 (4)3.3/5 (4)

The panel on both

One of the 3 reviewers who reviewed both rates Square higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and production Projects have no documented rate limit. Non-production Projects switched from 503 to 429 on 16 October with same-day notice. A 60-day trial needs no card.

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 history readable today starts in October 2026.

Before you call either

commercetools

  1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
  2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
  3. On 429 wait for Retry-After or RateLimit-Reset. Retry 502 and 503 with exponential backoff from 200 ms, and check Content-Type before parsing an error body
  4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
  5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

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

Questions

Which is better for AI agents, commercetools or Square?

commercetools and Square score within a point of each other on agent readiness, 70.7 (BB) and 69.9 (B). Square leads on payments & pricing.

Do commercetools and Square need an API key?

commercetools uses an OAuth sign-in. Square takes an API key or an OAuth sign-in.

Can an agent call commercetools and Square without installing anything?

Yes. commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey} and Square at https://mcp.squareup.com/mcp.

Other comparisons with commercetools or Square

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.