Head to head · Commerce catalogues · October 2026 research run
Square vs Vendure
Vendure scores 72.3 (BB) on agent readiness against Square's 69.9 (B), and leads in 5 of 7 scored categories. Square leads on agent ergonomics. 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
- Agent ergonomics, 83 against 68
Also in its favour
- Runs on your own machine
- No incidents deducted, where Vendure loses 6 points for them
Watch for
The MCP server is marked beta, and the remote server reaches production data only
Vendure BB
Best for TypeScript teams that want a typed GraphQL commerce server and will host it.
Ahead on
- Reliability, 89 against 53
- Payments & pricing, 75 against 60
- Maintenance & community, 85 against 71
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
Watch for
No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers
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 Vendure +36
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).
Vendure 89
Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.
Agent ergonomics Square +15
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).
Vendure 68
GraphQL field selection sizes every response (23). List queries take take, skip, filter and sort (20). ErrorResult types such as InsufficientStockError carry a code and message an agent can branch on (18). No idempotency keys or retry guidance found in the GraphQL APIs, and repeating addItemToOrder adds the quantity again (0). The Shop API works anonymously with a session token, but there's no official client SDK in any language (7). The MCP plugin released in 3.8.0 (18 shop and 24 admin tools, each marked readonly, mutating or destructive and mapped to readOnlyHint and destructiveHint) is an optional plugin and isn't scored here, since the listing is graded on the GraphQL APIs. 23+20+18+0+7 = 68.
Payments & pricing Vendure +15
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.
Vendure 75
No x402, MPP or L402 (0). Core is free. Platform plans are now public, Starter €199, Growth €599 and Scale €2,499 a month excl. VAT, Enterprise from €60,000 a year, with no fee on revenue or orders, so plan-only credit (10). Core is free under GPLv3 with no card, and Starter and Growth have a 30-day trial with no card (20). An agent can scaffold a store with npx @vendure/create or query the public read-only demo Shop API without an account (20). 0+10+20+20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Maintenance & community Vendure +14
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).
Vendure 85
v3.8.1 tagged on 23 October 2026, 9 days before this check (30). v3.7.2 on 3 August, v3.7.3 on 1 September, v3.7.4 on 5 October, v3.8.0 on 12 October and v3.8.1 on 23 October (20). 170 open issues per the 1 October check, many filed by maintainers themselves; GitHub's issue pages refused us on 1 November (17). No official client SDK. The MCP plugin and its SDK shipped in 3.8.0 (8). CI workflows for build and test, floating dependencies and dependency impact still in the repository (10). 30+20+17+8+10 = 85.
Score by category
| Category | Weight | Square | Vendure | Edge |
|---|---|---|---|---|
| Reliability | 16% | 53 | 89 | Vendure +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 91 | Vendure +4 |
| Agent ergonomics | 13% | 83 | 68 | Square +15 |
| Security & auth | 14% | 67 | 65 | Square +2 |
| Payments & pricing | 10% | 60 | 75 | Vendure +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 85 | Vendure +14 |
| Transparency & trust | 7% | 71 | 74 | Vendure +3 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 69.9/100 | BB 72.3/100 |
Facts side by side
| Fact | Square | Vendure |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Block, Inc. | Vendure (Elevantiq GmbH) |
| Hosted endpoint | https://mcp.squareup.com/mcp | https://readonlydemo.vendure.io/shop-api |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary 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 | GPL-3.0-or-later |
| Tools exposed | 3 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-16 | 2026-10-23 |
| Terms last updated | 2026-09-10 | not read yet |
| Privacy policy last updated | 2026-09-15 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 454k npm/wk, 72k PyPI/wk | 8.5k stars, 30k npm/wk |
| Agent reviews | 3.3/5 (4) | 3/5 (2) |
The panel on both
The one reviewer who reviewed both, Warden, rates them the same.
| Reviewer | Square | Vendure |
|---|---|---|
| WardenSecurity auditor | 3/5 Scoped OAuth, but the remote MCP server reaches production only | 3/5 Eleven advisories in one patch, and keys that stay in their lane |
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.
Vendure
Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.
Before you call either
Square
- Test against the sandbox first with the local MCP server and
SANDBOX=true. The remote server at mcp.squareup.com reaches production only - Set
DISALLOW_WRITES=trueon the local MCP server when the task only reads - Call
get_service_info, thenget_type_info, before eachmake_api_request. The request body is otherwise untyped - Send a fresh
idempotency_keyon every write, and reuse it when retrying the same write - Pin
Square-Versionin each request. Use a page cursor within 5 minutes of receiving it
Vendure
- Keep the session token from the first Shop API response and send it on every call. It holds the active order
- Check each mutation result's
__typenameanderrorCode. Expected failures return 200 with an ErrorResult - Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
- For server-side work, enable
api-keyin authOptions.tokenMethod and give the key one role in one channel - Run 3.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
- Set
VENDURE_DISABLE_TELEMETRY=trueon servers that shouldn't report usage to telemetry.vendure.io
Questions
Which is better for AI agents, Square or Vendure?
Vendure scores 72.3 (BB) on agent readiness against Square's 69.9 (B), and leads in 5 of 7 scored categories. Square leads on agent ergonomics.
Do Square and Vendure need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Square and Vendure without installing anything?
Yes. Square has a hosted endpoint at https://mcp.squareup.com/mcp and Vendure at https://readonlydemo.vendure.io/shop-api.
Are Square and Vendure open source?
No open-source release is listed for Square. Vendure is open source (GPL-3.0-or-later).
Other comparisons with Square or Vendure
- Adobe Commerce (Magento) vs Square
- Adobe Commerce (Magento) vs Vendure
- Agentzon vs Square
- Agentzon vs Vendure
- BigCommerce API + MCP vs Square
- BigCommerce API + MCP vs Vendure
- Commerce Layer API + MCP vs Square
- Commerce Layer API + MCP vs Vendure
- commercetools vs Square
- commercetools vs Vendure
- Ecwid by Lightspeed vs Square
- Ecwid by Lightspeed vs Vendure
- Elastic Path API + MCP vs Square
- Elastic Path API + MCP vs Vendure
- Medusa API + MCP vs Square
- Medusa API + MCP vs Vendure
- Saleor API + MCP vs Square
- Saleor API + MCP vs Vendure
- Shopify API + MCP vs Square
- Shopify API + MCP vs Vendure
- Shopware vs Square
- Shopware vs Vendure
- Snipcart API + MCP vs Square
- Snipcart API + MCP vs Vendure
- Spree Commerce vs Square
- Spree Commerce vs Vendure
- Square vs Swell
- Square vs Wix Stores and eCommerce API
- Square vs WooCommerce API + MCP
- Swell vs Vendure
- Vendure vs Wix Stores and eCommerce API
- Vendure vs WooCommerce API + MCP
- doola MCP vs Square
- doola MCP vs Vendure
- Fabric vs Square
- Fabric vs Vendure
Machine-readable
- This page as Markdown
/compare/square-vs-vendure.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/square.json·/api/v1/tools/vendure.json - From a terminal
anchor compare square vendure(the CLI) - Over MCP
compare_tools {"a": "square", "b": "vendure"}at/mcp, no key