Head to head · Commerce catalogues · October 2026 research run

Commerce Layer API + MCP vs Saleor API + MCP

Saleor API + MCP scores 76.5 (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 75

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

Saleor API + MCP BB

Best for Teams that want an open-source GraphQL backend with multi-channel pricing and an agent that reads store data safely.

Ahead on

  • Schema & documentation, 89 against 83
  • Agent ergonomics, 86 against 69
  • Security & auth, 71 against 64
  • Payments & pricing, 68 against 38
  • Transparency & trust, 76 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

The MCP server can't create checkouts or orders

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 Saleor API + MCP +30

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.

Saleor API + MCP 68

No x402, MPP or L402 (0). Cloud plans are public, Select $1,599 a month to $200,000 GMV and Volume $3,999 to $1,000,000, with 0.8% and 0.4% overage, but there's no per-call or per-unit price (10). The BSD core is free to self-host, and Cloud sandboxes are free for non-commercial use with no card mentioned (20). An agent can run the core from the Docker image with no account, but Cloud needs a browser signup (15). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Agent ergonomics Saleor API + MCP +17

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.

Saleor API + MCP 86

GraphQL field selection sizes every response, and the MCP server has 8 compact tools (25). Cursor pagination capped at 100, with filter, where, search and sort inputs (20). Mutations return typed errors with a code, field and message (18). Payment transaction mutations take an idempotencyKey, and 7 of the 8 MCP tools declare readOnlyHint and idempotentHint (the eighth only returns the API URL) (15). MCP tools default to 100 items and need only a channel. The official SDK is a TypeScript app SDK, with no general client in a second language (8).

Transparency & trust Saleor API + MCP +17

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.

Saleor API + MCP 76

BSD-3-Clause core, with the MCP server under AGPL-3.0 (30). Privacy policy updated 8 August 2025 names Saleor Commerce sp. z o.o. in Wrocław, links a subprocessor list and states 30 days for cookies, but no DPA is linked from it and other retention is "not longer than necessary" (20). Deprecations are marked in the schema and removed in a named later version, with upgrade guides, but notices carry versions rather than dates (15). Self-hosted servers send daily usage telemetry by default (counts of products, attributes and models, plus version), described on a Usage Telemetry docs page and turned off with SEND_USAGE_TELEMETRY=False. Cloud subprocessors are listed (18).

Reliability Commerce Layer API + MCP +13

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.

Saleor API + MCP 75

Graded on Saleor Cloud. Status page at status.saleor.io with an incident feed and history (20). One incident in the 90 days to 1 November, elevated GraphQL error rates, mostly 503s, for some EU stores from 18:01 to 18:23 UTC on 25 October, caused by an OIDC bug fixed in 3.23.45. Partial and 22 minutes, so minor (20). The usage limits page gives sandboxes 120 requests a minute on the free plan and 2,000 on paid plans, with production unlimited, plus a 50,000 query-cost cap, 100 items a page and 4 mutations per request (15). Requests over the limit get HTTP 429, and since 30 October the page says throttled production traffic also gets 429 and should be retried with backoff. Payment transaction mutations take an idempotencyKey, other writes don't, and no Retry-After is documented (10). No SLA on the pricing page (0). Generally available (10).

Security & auth Saleor API + MCP +7

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

Saleor API + MCP 71

App tokens limited to named permissions such as MANAGE_PRODUCTS and MANAGE_ORDERS, revocable through the API, and short-lived staff JWTs with refresh. Tokens travel in headers, never the URL (27). The MCP server never runs mutations, and a self-run copy can pin allowed API domains with ALLOWED_DOMAIN_PATTERN (16). Tools return merchant- and shopper-entered text, marked openWorldHint, with no prompt-injection guidance found (5). Observability webhooks can report API calls, but no operator audit log of who did what was found (8). SECURITY.md routes reports through GitHub advisories or security@saleor.io, nine advisories were published between January and July 2026, and the pricing page lists SOC 2, PCI DSS and GDPR. No security.txt and no bounty (15).

Schema & documentation Saleor API + MCP +6

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.

Saleor API + MCP 89

One GraphQL schema with introspection, and a 954 KB SDL copy in the MCP repo (25). llms.txt split into per-section indexes (10). Fields and mutations carry descriptions, doc categories and deprecation reasons, but rarely say when not to use them (13). Strict GraphQL types with 78 error-code enums and required markers (14). Typed error codes on every mutation payload, with examples in the docs (12). CHANGELOG with a breaking changes section per minor version, GitHub releases, and 464 @deprecated markers in the schema (15).

Score by category

CategoryWeightCommerce Layer API + MCPSaleor API + MCPEdge
Reliability16%8875Commerce Layer API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8389Saleor API + MCP +6
Agent ergonomics13%6986Saleor API + MCP +17
Security & auth14%6471Saleor API + MCP +7
Payments & pricing10%3868Saleor API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Saleor API + MCP +3
Transparency & trust7%5976Saleor API + MCP +17
Negative events≤15-3-2
TotalB 67.6/100BB 76.5/100

Facts side by side

FactCommerce Layer API + MCPSaleor API + MCP
KindHTTP APIHTTP API
VendorCommerce LayerSaleor
Hosted endpointhttps://core.commercelayer.io/api/public/resourcesno (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneBSD-3-Clause
Tools exposed118
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-272026-10-28
Terms last updated2026-05-01no date given
Privacy policy last updatedno date givenno 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 benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity7.3k npm/wk23k stars, 7.3k npm/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

Saleor API + MCP

One GraphQL schema with 78 typed error-code enums and 464 marked deprecations. The MCP server can't create checkouts or orders.

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

Saleor API + MCP

  1. Pass the channel slug on product and checkout queries. Prices and availability are per channel
  2. Send X-Saleor-API-URL and X-Saleor-Auth-Token on every MCP request, with a token holding MANAGE_PRODUCTS and MANAGE_ORDERS
  3. Read the errors array in every mutation payload. A 200 response can still carry a CheckoutErrorCode
  4. Keep queries under the 50,000 complexity cap and 100 items a page, and send at most 4 mutations per request
  5. The 3.24 changelog removes the old dummy payment plugins, so test checkouts should use a payment app
  6. On a sandbox stay under 120 requests a minute (2,000 on paid plans), and retry an HTTP 429 with backoff

Questions

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

Saleor API + MCP scores 76.5 (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 Saleor API + MCP need an API key?

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

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

Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources. No hosted endpoint is listed for Saleor API + MCP.

Are Commerce Layer API + MCP and Saleor API + MCP open source?

No open-source release is listed for Commerce Layer API + MCP. Saleor API + MCP is open source (BSD-3-Clause).

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