Head to head · Commerce catalogues · October 2026 research run

BigCommerce API + MCP vs Commerce Layer API + MCP

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Commerce Layer API + MCP's 67.6 (B), and leads in 3 of 7 scored categories. Commerce Layer API + MCP leads on reliability, 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

BigCommerce API + MCP B

Best for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP.

Ahead on

  • Security & auth, 70 against 64
  • Payments & pricing, 60 against 38
  • Transparency & trust, 77 against 59

Also in its favour

  • No incidents deducted, where Commerce Layer API + MCP loses 3 points for them

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

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 77
  • Schema & documentation, 83 against 66
  • Agent ergonomics, 69 against 62

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

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

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 BigCommerce API + MCP +22

BigCommerce API + MCP 60

No x402, MPP or L402 (0). Plan prices public, Core $39, Growth $105 and Scale $399 a month with GMV caps and 2.0, 1.0 and 0.6 per cent on orders through non-embedded providers, but nothing per call (10). 15-day free trial, and the pricing page says no credit card is needed (20). An agent can shop any store that has switched on the MCP as a guest with no key, but back-office access needs a person to create an API account (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Transparency & trust BigCommerce API + MCP +18

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

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.

Schema & documentation Commerce Layer API + MCP +17

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

Commerce Layer API + MCP 83

OpenAPI 3.0 file served without auth at data.commercelayer.app (25). llms.txt and Markdown docs (10). Core MCP tool descriptions are one line each, and the API reference covers each resource, with little on when not to use a call (13). Typed JSON:API attributes in the spec, but MCP writes take a free-form attributes object that preflight checks against the schema (11). Per-resource examples in the reference and JSON:API error objects (11). A dated public changelog tags breaking changes, and an upcoming-changes page lists breaks ahead of release. Since 5 October 2026 the Core API takes a date-stamped version in the path (2017-08 stays the default, 2026-05 is new), and responses carry api_version, api_versions and deprecation warnings. Breaking changes on 16 June, 27 August and 2 September 2026 still shipped on the day they were announced (13). 25+10+13+11+11+13 = 83.

Reliability Commerce Layer API + MCP +11

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

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.

Agent ergonomics Commerce Layer API + MCP +7

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

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.

Security & auth BigCommerce API + MCP +6

BigCommerce API + MCP 70

API accounts issue a token limited by OAuth scopes chosen at creation and revocable by deleting the account, but tokens never expire and can't be rotated in place (24). Read-only scope variants, and the storefront MCP has no back-office tools, so a guest agent can only shop. The invite-only Store Management MCP beta adds OAuth 2.1 with PKCE, per-scope grants that start at none, products and promotions created hidden or disabled, and refunds only after a quote, but it isn't generally available, so it moves no line (16). The MCP returns merchant product content with no prompt-injection guidance found (5). The store logs API (GET /v3/store/systemlogs) keeps storefront events such as order status changes for 365 days, and the control panel keeps staff action logs (a status incident on 8 July names them). No per-call API log found (8). Trust centre lists PCI DSS Level 1 as merchant and service provider, SOC 1, SOC 2 and SOC 3, ISO/IEC 27001:2022 with 27017, 27018 and 27701, and a vulnerability disclosure programme run through Inspectiv. No security.txt (404 on 2 November) (17).

Commerce Layer API + MCP 64

OAuth 2.0 tokens throughout. Integration credentials follow a custom role set per resource and per operation, sales channel tokens are scoped to a market, and the Core MCP accepts the same tokens or runs the OAuth flow (28). The docs tell you to give the agent a dedicated role with minimal permissions, but delete_resource has no documented confirmation step (12). Tool results include merchant- and shopper-entered data with no prompt-injection guidance found (5). The versions endpoint, which gave change history per resource, was removed on 8 May 2026. Event stores remain, with a retention policy added on 18 June, but since 2 September 2026 they and the Dashboard resource inspector are Enterprise only (6). SOC 2 Type 2, ISO 27001 and PCI DSS Level 1 claimed on the security page, with annual penetration tests and fixes within 90 days. The SDK's SECURITY.md gives two email addresses. No security.txt and no bug bounty found (13).

Score by category

CategoryWeightBigCommerce API + MCPCommerce Layer API + MCPEdge
Reliability16%7788Commerce Layer API + MCP +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6683Commerce Layer API + MCP +17
Agent ergonomics13%6269Commerce Layer API + MCP +7
Security & auth14%7064BigCommerce API + MCP +6
Payments & pricing10%6038BigCommerce API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8282even
Transparency & trust7%7759BigCommerce API + MCP +18
Negative events≤150-3
TotalB 69.9/100B 67.6/100

Facts side by side

FactBigCommerce API + MCPCommerce Layer API + MCP
KindHTTP APIHTTP API
VendorBigCommerce (Commerce.com)Commerce Layer
Hosted endpointhttps://api.bigcommerce.comhttps://core.commercelayer.io/api/public/resources
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidFreemium
x402nono
Tools exposed711
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-27
Terms last updated2026-06-012026-05-01
Privacy policy last updated2026-01-28no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone7.3k npm/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Commerce Layer API + MCP 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

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.

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.

Before you call either

BigCommerce API + MCP

  1. Give the agent a store-level API account with only the scopes the task needs, and delete it when done
  2. On a 429, wait X-Rate-Limit-Time-Reset-Ms before retrying
  3. Expect up to 10 minutes after a store owner enables the MCP before the URL answers
  4. The MCP stops at a checkout URL. Payment happens in the shopper's browser
  5. Point a coding agent at the docs MCP at https://docs.bigcommerce.com/_mcp/server
  6. 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

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

Questions

Which is better for AI agents, BigCommerce API + MCP or Commerce Layer API + MCP?

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Commerce Layer API + MCP's 67.6 (B), and leads in 3 of 7 scored categories. Commerce Layer API + MCP leads on reliability, schema & documentation and agent ergonomics.

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

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

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

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

Other comparisons with BigCommerce API + MCP or Commerce Layer API + MCP

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.