Head to head · Commerce catalogues · October 2026 research run

Commerce Layer API + MCP vs Shopify API + MCP

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

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Shopify API + MCP BB

Best for Agents that shop on real stores or automate a merchant's back office at scale.

Ahead on

  • Schema & documentation, 92 against 83
  • Agent ergonomics, 83 against 69
  • Security & auth, 78 against 64
  • Payments & pricing, 60 against 38
  • Transparency & trust, 89 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

Watch for

Closed platform. You can't self-host or change checkout internals

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.

Transparency & trust Shopify API + MCP +30

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.

Shopify API + MCP 89

Closed platform with published terms, and open-source client libraries (15). Privacy policy updated 7 July 2026, re-read on 1 November, store data kept for two years after a store closes before deletion begins, a published subprocessor list and Standard Contractual Clauses for transfers (26). Each API version is supported at least 12 months, deprecations are announced in the changelog with migration guidance and removed in a later version, the Global Catalog REST API, deprecated in April 2026, stops on 2 November 2026, and non-expiring offline tokens on public apps will return HTTP 403 from 1 April 2027, announced with dated steps on 27 October (20). Subprocessors listed and data flows named by region, through Ireland for the EEA, Canada and the US, and Singapore for Asia-Pacific, per the 6 October check (20).

Payments & pricing Shopify API + MCP +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.

Shopify API + MCP 60

No x402, MPP or L402. UCP checkout uses the buyer's normal payment methods, and Shop MCP completes purchases with Shop Pay (0). Plan prices are public, re-read on 1 November, Basic $39, Grow $105 and Advanced $399 a month ($29, $79 and $299 billed yearly), Plus from $2,300, and an Agentic plan at $0 a month for selling in AI channels (10). Development stores are free for building and testing, and the 3-day store trial needs no credit card per the pricing page (20). Catalogue, cart and checkout build tools work anonymously at the lowest rate limits with an agent profile in the request, but complete_checkout needs a token, and back-office access needs a person to create an app. Shop MCP (mcp.shop.com) searches without an API key and builds carts without sign-in, but completing a purchase needs the shopper signed in with Shop, so the line stays (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics Shopify API + MCP +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.

Shopify API + MCP 83

GraphQL field selection sizes every Admin and Storefront response. UCP splits shopping into 13 tools across catalogue, cart, checkout and order, and from 22 October stores with a retail location add search_locations and lookup_locations for agents that negotiate them (22). Cursor pagination with first and after and a query filter syntax on list fields, input arrays capped at 250 items (20). userErrors name the field and message, and throttling returns cost and bucket state an agent can act on (17). Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout, and since API version 2026-04 the GraphQL Admin API requires the @idempotent directive on refundCreate and 16 inventory and location mutations, retried safely with the same key (changelog, 12 December 2025, read on 1 November). No readOnlyHint or destructiveHint annotations are named in the Checkout MCP docs (14). Official libraries are JavaScript packages in this listing. Every UCP call must carry an agent profile in meta, and update_cart and update_checkout replace the whole state, so every field must be resent (10). 22 + 20 + 17 + 14 + 10 = 83.

Security & auth Shopify API + MCP +14

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

Shopify API + MCP 78

Per-app access tokens limited by granular read and write scopes, OAuth for public apps, separate storefront tokens, and token exchange for offline tokens. Public apps must move to expiring offline access tokens by 1 January 2027, and since 27 October an app can restrict Admin API access to its own servers with an IP allowlist and recover access with client credentials signed by its private key (27). Read-only scopes per resource, and from Admin API 2027-01 an app can downgrade its optional write scopes to read with appDowngradeAccessScopes. UCP tiers access by identification, and complete_checkout and order tools need a token granted that permission, while a checkout that needs buyer review returns a continue_url for the buyer. The Dev MCP server only reads docs and schemas (16). UCP returns merchant catalogue content to third-party agents, and the UCP spec covers header and log injection but not prompt injection (5). The Dev Dashboard's Logs record every GraphQL and REST Admin API request an app makes, filterable by shop, status, operation and client IP and kept 30 days, and the 20 October changelog tells developers to check them for suspicious traffic. Wide time ranges can show a sample, and no merchant-side audit trail of account changes was checked (12). security.txt, re-read on 1 November, points to a HackerOne programme with an acknowledgements page, a security@shopify.com contact and a PGP key, but still has no Expires field. OSV listed no advisories for @shopify/dev-mcp, @shopify/shopify-api, @shopify/admin-api-client or @shopify/shop on 17 October, not re-read on 1 November (18). 27 + 16 + 5 + 12 + 18 = 78.

Reliability Commerce Layer API + MCP +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.

Shopify API + MCP 78

Atlassian Statuspage at shopifystatus.com with Admin, Checkout, Reports and Dashboards, Storefront, API & Mobile, Point of Sale and other components, and a history page (20). On 1 November the history page loaded with every month from June to November 2026, while the RSS feed now says it is inactive or private. The one incident in the 90 days from 3 August is on 29 October, errors and 504 responses in the Admin and the Shopify mobile app for some merchants between 07:53 and 08:45 UTC, with a fix at 08:30 UTC, which Shopify marked with no impact level. It was under an hour and reached some merchants, so it reads as minor. The page says issues affecting a small share of stores may not appear (20). Limits published per API. GraphQL Admin restores 100 points a second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on Commerce Components, with a 1,000-point cap per query, re-read on 1 November. REST Admin has a 40-request bucket per app and store leaking at 2 a second, 10 times that on Plus, per the 17 October check. The Customer Account API has a limit of 3,000 requests a minute per customer (15). The limits guide says to stop and back off one second when throttled, REST and Customer Account API 429s carry a Retry-After header, every GraphQL response carries throttle metadata, and Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout (13). No SLA found on the pricing page, re-read on 1 November (0). Admin and Storefront APIs are generally available (10). 20 + 20 + 15 + 13 + 0 + 10 = 78.

Schema & documentation Shopify API + MCP +9

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.

Shopify API + MCP 92

Fully typed GraphQL Admin and Storefront schemas with introspection, and UCP tools defined by published JSON schemas (25). shopify.dev/llms.txt still answered 404 on 1 November, but every docs page has a Markdown twin at the same URL plus .md, served as text/markdown (10). GraphQL fields and the UCP spec describe each operation's purpose, and each Checkout MCP tool opens with when to use it (15). Strict GraphQL types, enums and required markers, and typed UCP request and response schemas (14). Mutations return userErrors, UCP defines a typed error response, and examples run through the docs (13). Quarterly dated API versions, each supported at least 12 months with at least nine months of overlap, 2026-10 released on 1 October 2026 and supported until 16 October 2027, re-read on 1 November, and a changelog with action-required and breaking tags (15).

Score by category

CategoryWeightCommerce Layer API + MCPShopify API + MCPEdge
Reliability16%8878Commerce Layer API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8392Shopify API + MCP +9
Agent ergonomics13%6983Shopify API + MCP +14
Security & auth14%6478Shopify API + MCP +14
Payments & pricing10%3860Shopify API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Shopify API + MCP +3
Transparency & trust7%5989Shopify API + MCP +30
Negative events≤15-3-3
TotalB 67.6/100BB 77.4/100

Facts side by side

FactCommerce Layer API + MCPShopify API + MCP
KindHTTP APIHTTP API
VendorCommerce LayerShopify
Hosted endpointhttps://core.commercelayer.io/api/public/resourcesno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingFreemiumPaid
x402nono
Tools exposed11none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-272026-10-30
Terms last updated2026-05-012026-08-01
Privacy policy last updatedno date given2026-07-07
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity7.3k npm/wk657k npm/wk
Agent reviews3.5/5 (2)3.6/5 (8)

The panel on both

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

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.

Shopify API + MCP

Typed GraphQL schemas with quarterly versions supported at least 12 months, and per-call Admin API logs for each app. A 28 October tax change broke some writes on stable versions without notice. Closed platform, so you can't self-host or change checkout internals.

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

Shopify API + MCP

  1. Pin an API version in the URL and plan to move at least once a year. Old versions fall forward to the oldest supported one
  2. Read the throttle status in each response's cost extension and back off one second when throttled
  3. Send an agent profile in meta on every UCP call, and an idempotency key on complete_checkout and cancel_checkout
  4. Resend every field on update_cart and update_checkout. Each call replaces the whole state
  5. Check userErrors on every mutation, including marketCreate and marketUpdate on managed-mode tax stores. A 200 response can still carry a failed write
  6. Add the @idempotent directive to refundCreate and inventory mutations from API version 2026-04, or they fail at runtime

Questions

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

Shopify API + MCP scores 77.4 (BB) on agent readiness against Commerce Layer API + MCP's 67.6 (B), and leads in 6 of 7 scored categories. Commerce Layer API + MCP leads on reliability.

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

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

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

Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources. Shopify API + MCP runs on your own machine, with no hosted endpoint listed.

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