Head to head · Commerce catalogues · October 2026 research run
BigCommerce API + MCP vs Square
BigCommerce API + MCP and Square score within a point of each other on agent readiness, 69.9 (B) and 69.9 (B). Square leads on schema & documentation and agent ergonomics. Both do commerce catalogues.
Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons
Which one, for what
Best for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP.
Ahead on
- Reliability, 77 against 53
- Maintenance & community, 82 against 71
- Transparency & trust, 77 against 71
Watch for
The storefront MCP has no back-office tools and documents no tool annotations; back-office tools are only in an invite-only closed beta
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 66
- Agent ergonomics, 83 against 62
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
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 BigCommerce API + MCP +24
BigCommerce API + MCP 77
Atlassian Statuspage at status.bigcommerce.com with API & Webhooks, Checkout & Payment Processing, Storefront and B2B components, a history page and an Atom feed (20). Read on 2 November, the history holds 36 incidents from 4 August, 8 in August, 8 in September and 20 in October. Seven carry a major or critical label, each partial by its own text. Microsoft single sign-on failed for a subset of stores for 29 minutes (25 August), Modern Import/Export catalogue export failed for 65 minutes (14 September), the Contact Center phone system was down (16 September, not the platform), category pages showed inaccurate stock (23 September), QuickBooks Payments stores couldn't take payments for 3 hours 39 minutes (5 October, one provider), some Chrome on Android shoppers on headless storefronts couldn't reach checkout (26 October), and Bolt payments failed for 2 hours 12 minutes after Bolt changed its domain (27 October, one provider). Search returned HTTP 500s across the platform for 66 minutes on 27 October, search only, and Management API add-to-cart requests failed for 59 minutes on 12 October. The 10 July availability major left the window on 8 October, so with only partial incidents the line is 20 (was 10, cause time). Published limits, 450 requests per 30 seconds on Scale and 150 on Growth and Core, refreshed every 30 seconds (15). A 429 carries X-Rate-Limit-Time-Reset-Ms and the docs advise waiting that long, then backing off exponentially. No idempotency keys for writes found (12). No SLA found (0). REST APIs are generally available, and the storefront MCP pages no longer carry a beta label, with the server switched on from the standard Settings, API and MCP page. The invite-only Store Management MCP beta isn't graded (10).
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).
Schema & documentation Square +21
BigCommerce API + MCP 66
Reference pages are built from API specs (a 29 September changelog entry corrected twenty of them), but the public spec repo was archived in December 2023 and its successor, bigcommerce/docs, still asked git for credentials on 2 October, so no current spec file was found (10). llms.txt hub linking a developer index of about 500 Markdown pages, plus a docs MCP server (10). Reference descriptions say what each call does, and the MCP tools are guest shopping steps (12). Typed REST parameters in the reference (11). Examples in the reference, but the developer index has no page on error responses (10). Dated changelog with entries almost daily, v2 and v3 REST paths, and a Deprecations and Sunsets page, though it gives no notice period (13).
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).
Agent ergonomics Square +21
BigCommerce API + MCP 62
The B2C storefront MCP reference lists 7 compact, shopping-only tools, and search_products pages with a cursor (23). REST listings take page and limit, with filters such as id:in, type and severity on the store logs endpoint, and the GraphQL Storefront API documents pagination (16). 429 handling is documented, but we found no error-format reference in the docs index (10). No idempotency keys, and the MCP reference documents no tool annotations (0). Guest MCP needs no key. Official API clients for Python, PHP, Ruby and Node, three updated in 2026 and the Python client last in January 2024 (13).
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).
Maintenance & community BigCommerce API + MCP +11
BigCommerce API + MCP 82
Changelog entries on 30 October 2026 (30). Entries on 28, 29 and 30 October alone, and many more since 4 August (20). Public changelog and a support centre (12). Neither MCP server is in the official registry. Official API clients updated in March 2026 (PHP), May 2026 (Ruby) and August 2026 (Node), while the Python client's last release was 0.23.4 in January 2024, per the 1 October check (12). Catalyst repo runs end-to-end tests on main, per the 1 October check (8).
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 BigCommerce API + MCP +6
BigCommerce API + MCP 77
Closed platform with published terms, now on commerce.com, and an open-source Catalyst storefront (15). The trust centre lists a DPA and a subprocessor document. The commerce.com privacy policy wasn't read in either pass (22). A Deprecations and Sunsets page lists deprecated v2 endpoints and three dated sunsets, the last on 3 June 2024, but the current deprecations carry no sunset dates and no notice period is stated (10). Subprocessor document listed and Google Cloud named as the host (18).
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
| Category | Weight | BigCommerce API + MCP | Square | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 53 | BigCommerce API + MCP +24 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 87 | Square +21 |
| Agent ergonomics | 13% | 62 | 83 | Square +21 |
| Security & auth | 14% | 70 | 67 | BigCommerce API + MCP +3 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 71 | BigCommerce API + MCP +11 |
| Transparency & trust | 7% | 77 | 71 | BigCommerce API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.9/100 | B 69.9/100 |
Facts side by side
| Fact | BigCommerce API + MCP | Square |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BigCommerce (Commerce.com) | Block, Inc. |
| Hosted endpoint | https://api.bigcommerce.com | https://mcp.squareup.com/mcp |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | none | 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 |
| Tools exposed | 7 | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-09-16 |
| Terms last updated | 2026-06-01 | 2026-09-10 |
| Privacy policy last updated | 2026-01-28 | 2026-09-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 454k npm/wk, 72k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.3/5 (4) |
The panel on both
The one reviewer who reviewed both, Warden, rates them the same.
| Reviewer | BigCommerce API + MCP | Square |
|---|---|---|
| WardenSecurity auditor | 3/5 Scoped tokens that never expire | 3/5 Scoped OAuth, but the remote MCP server reaches production only |
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
BigCommerce API + MCP
Rate limits are published per plan, and every 429 carries X-Rate-Limit-Time-Reset-Ms. Status incidents since August were partial. The storefront MCP lets a guest agent shop with no key but documents no tool annotations, back-office MCP tools are in an invite-only beta, and REST tokens never expire.
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
BigCommerce API + MCP
- Give the agent a store-level API account with only the scopes the task needs, and delete it when done
- On a 429, wait X-Rate-Limit-Time-Reset-Ms before retrying
- Expect up to 10 minutes after a store owner enables the MCP before the URL answers
- The MCP stops at a checkout URL. Payment happens in the shopper's browser
- Point a coding agent at the docs MCP at https://docs.bigcommerce.com/_mcp/server
- Store Management MCP is invite-only; if granted, call get_refund_quote and confirm with a person before create_refund, which the docs say is never safe to retry
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
Questions
Which is better for AI agents, BigCommerce API + MCP or Square?
BigCommerce API + MCP and Square score within a point of each other on agent readiness, 69.9 (B) and 69.9 (B). Square leads on schema & documentation and agent ergonomics.
Do BigCommerce API + MCP and Square need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call BigCommerce API + MCP and Square without installing anything?
Yes. BigCommerce API + MCP has a hosted endpoint at https://api.bigcommerce.com and Square at https://mcp.squareup.com/mcp.
Other comparisons with BigCommerce API + MCP or Square
- Adobe Commerce (Magento) vs BigCommerce API + MCP
- Adobe Commerce (Magento) vs Square
- Agentzon vs BigCommerce API + MCP
- Agentzon vs Square
- BigCommerce API + MCP vs Commerce Layer API + MCP
- BigCommerce API + MCP vs commercetools
- BigCommerce API + MCP vs Ecwid by Lightspeed
- BigCommerce API + MCP vs Elastic Path API + MCP
- BigCommerce API + MCP vs Fabric
- BigCommerce API + MCP vs Medusa API + MCP
- BigCommerce API + MCP vs Saleor API + MCP
- BigCommerce API + MCP vs Shopify API + MCP
- BigCommerce API + MCP vs Shopware
- BigCommerce API + MCP vs Snipcart API + MCP
- BigCommerce API + MCP vs Spree Commerce
- BigCommerce API + MCP vs Swell
- BigCommerce API + MCP vs Vendure
- BigCommerce API + MCP vs Wix Stores and eCommerce API
- BigCommerce API + MCP vs WooCommerce API + MCP
- Commerce Layer API + MCP vs Square
- commercetools vs Square
- Ecwid by Lightspeed vs Square
- Elastic Path API + MCP vs Square
- Medusa API + MCP vs Square
- Saleor API + MCP vs Square
- Shopify API + MCP vs Square
- Shopware vs Square
- Snipcart API + MCP vs Square
- Spree Commerce vs Square
- Square vs Swell
- Square vs Vendure
- Square vs Wix Stores and eCommerce API
- Square vs WooCommerce API + MCP
- BigCommerce API + MCP vs doola MCP
- doola MCP vs Square
- Fabric vs Square
Machine-readable
- This page as Markdown
/compare/bigcommerce-vs-square.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bigcommerce.json·/api/v1/tools/square.json - From a terminal
anchor compare bigcommerce square(the CLI) - Over MCP
compare_tools {"a": "bigcommerce", "b": "square"}at/mcp, no key