Get an audit

Head to head · Commerce products · October 2026 research run

Commerce Layer API + MCP vs commercetools

commercetools scores 71.3 (BB) on agent readiness against Commerce Layer API + MCP's 63.7 (B), and leads in 6 of 7 scored categories. Commerce Layer API + MCP leads on payments & pricing. Both do commerce products.

Commerce Layer API + MCPCommerce Layer · HTTP API B63.7/100#269 of 629 commercetoolscommercetools GmbH · HTTP API BB71.3/100#110 of 629

Which one, for what

Commerce Layer API + MCP B

Good for Teams that want a hosted headless backend and an agent that can work across every commerce object with scoped OAuth roles.

Ahead on

  • Payments & pricing, 25 against 20

Watch for

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

commercetools BB

Good for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.

Ahead on

  • Schema & documentation, 86 against 79
  • Agent ergonomics, 83 against 64
  • Security & auth, 70 against 64
  • Transparency & trust, 81 against 57

Also in its favour

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

Watch for

No public price. The pricing page describes order-based pricing and sends buyers to sales

Score by category

CategoryWeight this runCommerce Layer API + MCPcommercetoolsEdge
Reliability16%207073commercetools +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27986commercetools +7
Agent ergonomics13%16.26483commercetools +19
Security & auth14%17.56470commercetools +6
Payments & pricing10%12.52520Commerce Layer API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88285commercetools +3
Transparency & trust7%8.85781commercetools +24
Negative events≤1500
Total63.7 · B71.3 · BB

Facts side by side

FactCommerce Layer API + MCPcommercetools
KindHTTP APIHTTP API
VendorCommerce Layercommercetools GmbH
Hosted endpointhttps://core.commercelayer.io/api/public/resourceshttps://api.{region}.commercetools.com/{projectKey}
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MIT
Tools exposed11none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-292026-10-07
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 benchmarkingyesyes
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/wk221k npm/wk
Agent reviews3.5/5 (2)none

Verdicts

Commerce Layer API + MCP

Public OpenAPI 3.0 file and llms.txt. No price between the free plan and a sales-quoted Enterprise contract.

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and the HTTP API publishes no platform-wide rate limit. A 60-day trial needs no card.

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. Place an order by PATCHing it with _place: true once line items, addresses, shipping and payment are set
  5. Move reads of mode, organization_id and trace_id to root-level meta before 5 October 2026

commercetools

  1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
  2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
  3. Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body
  4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
  5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

Questions

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

commercetools scores 71.3 (BB) on agent readiness against Commerce Layer API + MCP's 63.7 (B), and leads in 6 of 7 scored categories. Commerce Layer API + MCP leads on payments & pricing.

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

Both use an OAuth sign-in.

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

Yes. Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources and commercetools at https://api.{region}.commercetools.com/{projectKey}.

Other comparisons with Commerce Layer API + MCP or commercetools

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.

Get an auditSee a sample report