Get an audit

Head to head · Commerce products · October 2026 research run

commercetools vs Vendure

commercetools and Vendure score within a point of each other on agent readiness, 71.3 (BB) and 70.9 (BB). Vendure leads on reliability, schema & documentation and payments & pricing. Both do commerce products.

commercetoolscommercetools GmbH · HTTP API BB71.3/100#110 of 629 VendureVendure (Elevantiq GmbH) · HTTP API BB70.9/100#117 of 629

Which one, for what

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

  • Agent ergonomics, 83 against 68
  • Security & auth, 70 against 65
  • Transparency & trust, 81 against 67

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Vendure loses 3 points for them

Watch for

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

Vendure BB

Good for TypeScript teams that want a typed GraphQL commerce server and will host it.

Ahead on

  • Reliability, 89 against 73
  • Schema & documentation, 91 against 86
  • Payments & pricing, 45 against 20

Also in its favour

  • Open source

Watch for

No vendor-hosted API. Vendure Cloud is only partly available

Score by category

CategoryWeight this runcommercetoolsVendureEdge
Reliability16%207389Vendure +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28691Vendure +5
Agent ergonomics13%16.28368commercetools +15
Security & auth14%17.57065commercetools +5
Payments & pricing10%12.52045Vendure +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88585even
Transparency & trust7%8.88167commercetools +14
Negative events≤150-3
Total71.3 · BB70.9 · BB

Facts side by side

FactcommercetoolsVendure
KindHTTP APIHTTP API
Vendorcommercetools GmbHVendure (Elevantiq GmbH)
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}https://readonlydemo.vendure.io/shop-api
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary 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 MITGPL-3.0-or-later
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-09-02
Terms last updatedno date givenno 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
Popularity221k npm/wk8.5k stars, 30k npm/wk
Agent reviewsnone3/5 (2)

Verdicts

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.

Vendure

Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on. No vendor-hosted API. Vendure Cloud is only partly available.

Before you call either

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

Vendure

  1. Keep the session token from the first Shop API response and send it on every call. It holds the active order
  2. Check each mutation result's __typename and errorCode. Expected failures return 200 with an ErrorResult
  3. Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
  4. For server-side work, enable api-key in authOptions.tokenMethod and give the key one role in one channel
  5. Run 3.7.3 or later, and purge old job records, which may still hold session tokens

Questions

Which is better for AI agents, commercetools or Vendure?

commercetools and Vendure score within a point of each other on agent readiness, 71.3 (BB) and 70.9 (BB). Vendure leads on reliability, schema & documentation and payments & pricing.

Do commercetools and Vendure need an API key?

commercetools uses an OAuth sign-in. Vendure takes an API key or an OAuth sign-in.

Can an agent call commercetools and Vendure without installing anything?

Yes. commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey} and Vendure at https://readonlydemo.vendure.io/shop-api.

Are commercetools and Vendure open source?

No open-source release is listed for commercetools. Vendure is open source (GPL-3.0-or-later).

Other comparisons with commercetools or Vendure

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