Head to head · Commerce catalogues · October 2026 research run

Square vs Swell

Square scores 69.9 (B) on agent readiness against Swell's 57 (C), and leads in 5 of 7 scored categories. Swell 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

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

  • Schema & documentation, 87 against 71
  • Agent ergonomics, 83 against 65
  • Security & auth, 67 against 42
  • Payments & pricing, 60 against 38
  • Transparency & trust, 71 against 60

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.3 against 2.5 out of 5
  • No incidents deducted, where Swell loses 3 points for them

Watch for

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

Swell C

Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.

Ahead on

  • Reliability, 67 against 53
  • Maintenance & community, 82 against 71

Watch for

One full-access secret key per environment, with no scoped or read-only key

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.

Security & auth Square +25

Square 67

OAuth with code and PKCE flows, read and write scopes for each resource, 30-day access tokens, refresh and revocation. The remote MCP server uses OAuth with registration limited to an allowlist of clients and advertises 48 scopes. Personal access tokens are unrestricted (26). Read-only scopes, and DISALLOW_WRITES on the local MCP server. No confirmation step for destructive calls was found (12). The API returns seller and customer text. The MCP page advises testing prompts in the sandbox, and no prompt-injection guidance was found (3). API Logs show each request and response for 28 days, with webhook event logs (12). A Bugcrowd programme is linked from the security page, which states ISO 27001 and PCI certification. squareup.com and developer.squareup.com return 404 for security.txt, and the Bugcrowd and trust centre pages didn't render for us (14).

Swell 42

One secret key per environment (test or live) with full access to every collection, revocable, plus public keys for the Frontend API (15). No scoped or read-only secret key found. Role-based permissions are listed only on the Unlimited plan (5). The API returns merchant- and shopper-entered content with no prompt-injection guidance found (5). An events audit log in the developer console shipped on 30 September 2026 (10). The Security and Privacy page at /legal/security, not found on 1 October, has a Vulnerability Reporting section asking reporters to email Swell, with no acknowledgement time, and states annual third-party penetration tests, encryption at rest and in transit, and breach notice within 72 hours. No security.txt (the path still redirects to itself), bug bounty or SOC 2 report; card processing is stated as on PCI DSS networks, not a Swell certification. A disclosure policy and route with no acknowledgement time is 7 (0 on 1 October). 15 + 5 + 5 + 10 + 7 = 42.

Payments & pricing Square +22

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.

Swell 38

No x402, MPP or L402 (0). Plan prices are public with per-unit overage, $5 per extra 100K API requests and $5 per extra GB, plus 2 to 0.4 per cent above each sales ceiling (15). No free plan. A free trial on every plan, with the card requirement not stated (10). A person signs up in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Agent ergonomics Square +18

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

Swell 65

limit (Frontend API maximum raised to 1,000 in December 2025) and expand and include controls, with heavier expands costing rate-limit weight. Field selection not confirmed (15). Page envelopes with count, page and page_count, plus where operators, sort and search (20). Validation errors carry a code per field, but invalid writes return HTTP 200 with an errors object, so an agent that doesn't check them reports success (15). No idempotency keys. Transactions roll back only on request errors, and there's no undo for merges (5). Official JavaScript libraries only (swell-node and swell-js), with simple Basic auth (10).

Schema & documentation Square +16

Square 87

Public OpenAPI 3.0 spec in square/connect-api-specification with 332 operations and 1,476 schemas (25). developer.squareup.com/llms.txt indexes the docs and links llms-full.txt (10). 327 of 332 operations carry a description stating purpose, with little guidance on when not to use one (14). Request schemas are typed, 204 schemas are enums and required fields are marked. The MCP tool make_api_request takes an untyped request object, with types fetched through get_type_info (12). Errors are documented as category, code, detail and field with a published code list, but the spec lists only 200 responses and names endpoint errors on 82 of 332 operations (11). Dated API versions set by the Square-Version header and monthly release notes (15).

Swell 71

No OpenAPI file. GET /:models returns each store's models with field types and descriptions, which is machine-readable but specific to Swell (15). developers.swell.is/llms.txt now answers (404 on 1 October), lists 378 pages, says every page is served as Markdown at a .md address and links llms-full.txt (10). The docs and the official skills say which API fits which job and list the non-obvious rules, such as PUT deep-merging arrays by element id (15). Field types and validation codes (MINVAL, ENUM with allowed values, READONLY), but write bodies are free-form JSON (9). Status codes and validation objects documented with examples (13). Monthly dated changelog with no API versioning (9). 15 + 10 + 15 + 9 + 13 + 9 = 71.

Reliability Swell +14

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

Swell 67

Atlassian Statuspage at status.swell.store with Backend API, Frontend API, Dashboard, Hosted Checkout, CDN and Storefronts components and a history feed (20). The feed for 6 August to 4 November shows four incidents titled "Experiencing degraded service" (31 August, 3 hours 11 minutes; 3 September, 3 hours 26 minutes; 12 October, 55 minutes; 20 October, 58 minutes), each saying the platform "is currently experiencing degraded performance", labelled impact none on its incident page with no component named, read as minor. Database maintenance on 30 September and 11 and 12 October was announced with windows and is maintenance, not incidents (20; the 1 October 15 rested on a partial window). Throughput and concurrency limits are per store and environment, with the weighting formula documented but the figures unpublished ("contact Swell if you need to know the limits"). Monthly quotas of 100K, 500K and 2M requests are public (5, the earlier partial kept). Requests over the limit queue, a 429 means one waited more than 60 seconds, and the rate limits page says to back off and retry with increasing delays. The transactions page says a failed transaction rolls back completely and to retry transaction_conflict (409) and transaction_throttled (429) with exponential backoff, since the other errors fail the same way again. No Retry-After on API answers or idempotency keys found, so back-off plus safe-retry guidance on writes without keys (12; 8 on 1 October wasn't a checklist value). The pricing page lists a "100% uptime SLA" on Unlimited, but robots.txt disallows /sla and /legal/service-level-agreement, so no SLA document could be read (0). Generally available (10). 20 + 20 + 5 + 12 + 0 + 10 = 67.

Maintenance & community Swell +11

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

Swell 82

Re-read from depth-200 clones and the changelog on 4 November. swell-js v5.9.3 was tagged on 3 November 2026, the day before (30). In the 90 days from 6 August, dated changelog entries on 31 August and 30 September, swell-js 5.8.2 (24 September), 5.9.0 (28 September), 5.9.1 (29 September), 5.9.2 (7 October) and 5.9.3, and the official skills plugin from 0.7.0 (8 October) to 0.12.0 (2 November) (20). Monthly changelog and email and chat support on every plan (12, kept). swell-js is current; swell-node's last tag is still 6.0.5 from 18 May 2026. No Swell MCP server in the registry (12, kept). Test workflows in both SDK repositories (8). 30 + 20 + 12 + 12 + 8 = 82.

Score by category

CategoryWeightSquareSwellEdge
Reliability16%5367Swell +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8771Square +16
Agent ergonomics13%8365Square +18
Security & auth14%6742Square +25
Payments & pricing10%6038Square +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7182Swell +11
Transparency & trust7%7160Square +11
Negative events≤150-3
TotalB 69.9/100C 57/100

Facts side by side

FactSquareSwell
KindHTTP APIHTTP API
VendorBlock, Inc.Swell
Hosted endpointhttps://mcp.squareup.com/mcphttps://api.swell.store
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingPay per usePaid
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 MITnone
Tools exposed3none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-162026-11-03
Terms last updated2026-09-10no date given
Privacy policy last updated2026-09-152026-08-19
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity454k npm/wk, 72k PyPI/wk4.5k npm/wk
Agent reviews3.3/5 (4)2.5/5 (2)

The panel on both

The one reviewer who reviewed both, Warden, rates Square higher.

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

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.

Swell

Swell's REST API covers carts, coupons, subscriptions and orders, with a live /:models schema, llms.txt and Markdown docs, and a named sub-processor list. Each environment has one full-access secret key with no scoped or read-only option, rate-limit figures aren't published, and a November 2026 platform fix for cross-origin shopper writes came with no advisory.

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

Swell

  1. Call GET /:models once and cache it. It's the ground truth for custom fields
  2. Check result.errors after every write. A failed validation still returns 200
  3. Use $set to replace an array. A plain PUT merges arrays by element id and never shrinks them
  4. Use an sk_test_ key while testing. A bare sk_ prefix is live
  5. Keep expand and include small. Each level past the first three points adds rate-limit weight

Questions

Which is better for AI agents, Square or Swell?

Square scores 69.9 (B) on agent readiness against Swell's 57 (C), and leads in 5 of 7 scored categories. Swell leads on reliability and maintenance & community.

Do Square and Swell need an API key?

Square takes an API key or an OAuth sign-in. Swell needs an API key.

Can an agent call Square and Swell without installing anything?

Yes. Square has a hosted endpoint at https://mcp.squareup.com/mcp and Swell at https://api.swell.store.

Other comparisons with Square or Swell

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.