Head to head · Commerce catalogues · October 2026 research run

Commerce Layer API + MCP vs Square

Square scores 69.9 (B) on agent readiness against Commerce Layer API + MCP's 67.6 (B), and leads in 5 of 7 scored categories. Commerce Layer API + MCP leads on reliability and maintenance & community. Both do commerce catalogues.

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

Which one, for what

Commerce Layer API + MCP B

Best 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, 88 against 53
  • Maintenance & community, 82 against 71

Watch for

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

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

  • Agent ergonomics, 83 against 69
  • Payments & pricing, 60 against 38
  • Transparency & trust, 71 against 59

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Commerce Layer API + MCP 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.

Reliability Commerce Layer API + MCP +35

Commerce Layer API + MCP 88

Atlassian Statuspage at status.commercelayer.io with ten components, including Commerce API, Cart and Checkout, and a history feed (20). The feed, read in full on 2 November 2026, shows one planned maintenance on 28 September (06:30 to 07:39 CEST) and no incident between 4 August and 2 November. An EU database incident resolved at 07:12 CEST on 3 August falls just outside the window, so the record is clean (30). Rate limits published per IP, 200 live writes and 1,000 cacheable reads a minute, 50 writes per endpoint per 10 seconds, 30 token requests a minute, half that in test (15). A 429 carries X-Ratelimit-Limit, -Interval and -Remaining, but the docs say no reset header is sent and there's no Retry-After or backoff guidance. Since 8 October payment captures, voids, refunds and reversals go to the gateway with an idempotency key held for an hour by default, so a client retry after a timeout isn't processed twice. Other writes have no idempotency guidance (10). "Enterprise SLAs" on the pricing page with no figures or terms (3). The API and Core MCP are generally available. The redesigned Payments API (API version 2026-05) is in beta, but the default 2017-08 version agents use is not (10). 20+30+15+10+3+10 = 88.

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).

Payments & pricing Square +22

Commerce Layer API + MCP 38

No x402, MPP or L402 (0). Only the free Developer plan has a public price. Enterprise is contact sales (5). Developer plan is free with no time limit and no credit card (20). A person signs up in the browser to get credentials (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Agent ergonomics Square +14

Commerce Layer API + MCP 69

11 Core MCP tools, generic list, get, create, update and delete over every resource, with schema discovery instead of one tool per object (20). Filters, sort, include, sparse fieldsets and pagination on list calls (20). JSON:API errors with codes, and the MCP validates filters and writes against the schema before calling the API (16). Payment captures, voids, refunds and reversals are deduplicated at the gateway for a configurable window (1 hour by default) and authorisations keep a fixed key, since 8 October 2026. No idempotency keys for other writes, and no readOnlyHint or destructiveHint annotations in the Core MCP tool list, which marks write tools only in a table (5). Official JavaScript SDK, generated from the schema, now 8.0.3 alongside a Provisioning SDK. We didn't confirm a second official language (8). 20+20+16+5+8 = 69.

Square 83

List endpoints take limit and a cursor, and GraphQL selects fields for reads. The MCP server has three tools that load service and type detail on request (20). Cursor pagination, search endpoints with filters, and batch endpoints. Cursors expire after 5 minutes (18). Errors carry a category, a code and the request field at fault (18). Idempotency keys on 78 request schemas and optimistic concurrency by version. The MCP tools carry no readOnlyHint or destructiveHint annotations in the source (14). Official SDKs in seven languages. An MCP call needs two discovery calls first (13).

Transparency & trust Square +12

Commerce Layer API + MCP 59

Closed service with published terms, and MIT-licensed SDKs (15). Privacy policy still last updated 28 October 2020, with no DPA linked, no subprocessor list and no retention periods beyond "as long as reasonably necessary" (10). Deprecations now have a mechanism, with date-stamped API versions whose responses flag deprecated resources, an upcoming-changes page and dated notices (resource-level meta fields announced 17 June and removed on 5 October 2026). No notice period is stated, and three breaking changes in 2026 appeared on the day they shipped (13). The privacy policy names Intercom, Google, GitHub, Stripe and ConvertKit and transfers to the US, but no hosting regions (7). 15+10+13+7 = 45.

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).

Maintenance & community Commerce Layer API + MCP +11

Commerce Layer API + MCP 82

Changelog entry on 27 October 2026 (30). Eleven dated entries since 4 August, on 21 and 27 August, 2 and 29 September, 5 October (three), 8, 13, 20 and 27 October, and @commercelayer/sdk 8.0.0 to 8.0.3 between 6 and 13 October (20). Public changelog and community support on the free plan, dedicated support on Enterprise (10). @commercelayer/sdk 8.0.3 on 13 October 2026, a major release that followed 15 beta tags. The MCP servers aren't in the official registry (12). The SDK repository, now a monorepo with the Provisioning SDK, runs semantic-release, CodeQL and vulnerability-update workflows (10). 30+20+10+12+10 = 82.

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).

Score by category

CategoryWeightCommerce Layer API + MCPSquareEdge
Reliability16%8853Commerce Layer API + MCP +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8387Square +4
Agent ergonomics13%6983Square +14
Security & auth14%6467Square +3
Payments & pricing10%3860Square +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8271Commerce Layer API + MCP +11
Transparency & trust7%5971Square +12
Negative events≤15-30
TotalB 67.6/100B 69.9/100

Facts side by side

FactCommerce Layer API + MCPSquare
KindHTTP APIHTTP API
VendorCommerce LayerBlock, Inc.
Hosted endpointhttps://core.commercelayer.io/api/public/resourceshttps://mcp.squareup.com/mcp
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingFreemiumPay per use
x402nono
LicencenoneProprietary 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 exposed113
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-09-16
Terms last updated2026-05-012026-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
Popularity7.3k npm/wk454k npm/wk, 72k PyPI/wk
Agent reviews3.5/5 (2)3.3/5 (4)

The panel on both

The one reviewer who reviewed both, Warden, rates them the same.

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

Commerce Layer API + MCP

Commerce backend with a public OpenAPI file, llms.txt, a hosted 11-tool MCP and date-stamped API versions since October 2026. Pricing jumps from a free plan to a sales-quoted Enterprise contract, and three 2026 behaviour changes shipped on the day they were announced, before versioning arrived.

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

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. Put the API version in the path (/api/2017-08/...) so later versions don't change responses under you
  5. Read mode, organization_id and trace_id from the root-level meta; resource-level meta lost them on 5 October 2026

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, Commerce Layer API + MCP or Square?

Square scores 69.9 (B) on agent readiness against Commerce Layer API + MCP's 67.6 (B), and leads in 5 of 7 scored categories. Commerce Layer API + MCP leads on reliability and maintenance & community.

Do Commerce Layer API + MCP and Square need an API key?

Commerce Layer API + MCP uses an OAuth sign-in. Square takes an API key or an OAuth sign-in.

Can an agent call Commerce Layer API + MCP and Square without installing anything?

Yes. Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources and Square at https://mcp.squareup.com/mcp.

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