Head to head · Commerce catalogues · October 2026 research run

Commerce Layer API + MCP vs Vendure

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

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

Vendure BB

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

Ahead on

  • Schema & documentation, 91 against 83
  • Payments & pricing, 75 against 38
  • Transparency & trust, 74 against 59

Also in its favour

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

Watch for

No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers

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 Vendure +37

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.

Vendure 75

No x402, MPP or L402 (0). Core is free. Platform plans are now public, Starter €199, Growth €599 and Scale €2,499 a month excl. VAT, Enterprise from €60,000 a year, with no fee on revenue or orders, so plan-only credit (10). Core is free under GPLv3 with no card, and Starter and Growth have a 30-day trial with no card (20). An agent can scaffold a store with npx @vendure/create or query the public read-only demo Shop API without an account (20). 0+10+20+20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Transparency & trust Vendure +15

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.

Vendure 74

GPL-3.0-or-later, with a commercial licence sold through Platform (30). Terms of Service and Privacy Policy, both version 2026-10-20, name Elevantiq GmbH trading as Vendure. The policy lists processors with locations (WorkOS, Amazon SES in Frankfurt, Vercel, Northflank in Frankfurt, Plausible, Sentry in the EU and others) and retention by category, such as 7 days for package download records and 12 months for licence-check IP addresses. Section 16 of the terms is a data processing agreement under Article 28 GDPR for support access on the self-serve plans, Vendure Cloud has its own, and the subprocessor list for that processing is given on request rather than published (25). SECURITY.md says only the latest 3.x minor gets fixes, and deprecations appear in the changelog without dated end-of-life notices (10). Core sends anonymous usage telemetry on by default since 3.6.0, at startup and about every 24 hours, to telemetry.vendure.io. The telemetry guide lists the fields (installation ID, versions, database type, plugin names, ranged entity counts), and VENDURE_DISABLE_TELEMETRY or a CI environment turns it off. Licence reports from Platform's commercial plugins don't follow that switch, which the terms say (20). The 1 October note said no usage telemetry was found in core, which was wrong. 30+25+10+20 = 85.

Schema & documentation Vendure +8

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.

Vendure 91

Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io, 997 lines on 1 November, including the MCP server guides (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an errorCode and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15).

Score by category

CategoryWeightCommerce Layer API + MCPVendureEdge
Reliability16%8889Vendure +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8391Vendure +8
Agent ergonomics13%6968Commerce Layer API + MCP +1
Security & auth14%6465Vendure +1
Payments & pricing10%3875Vendure +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8285Vendure +3
Transparency & trust7%5974Vendure +15
Negative events≤15-3-6
TotalB 67.6/100BB 72.3/100

Facts side by side

FactCommerce Layer API + MCPVendure
KindHTTP APIHTTP API
VendorCommerce LayerVendure (Elevantiq GmbH)
Hosted endpointhttps://core.commercelayer.io/api/public/resourceshttps://readonlydemo.vendure.io/shop-api
TransportsHTTP, Streamable HTTPHTTP
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneGPL-3.0-or-later
Tools exposed11none
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-272026-10-23
Terms last updated2026-05-01not read yet
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity7.3k npm/wk8.5k stars, 30k npm/wk
Agent reviews3.5/5 (2)3/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

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.

Vendure

Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.

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

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.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
  6. Set VENDURE_DISABLE_TELEMETRY=true on servers that shouldn't report usage to telemetry.vendure.io

Questions

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

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

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

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

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

Yes. Commerce Layer API + MCP has a hosted endpoint at https://core.commercelayer.io/api/public/resources and Vendure at https://readonlydemo.vendure.io/shop-api.

Are Commerce Layer API + MCP and Vendure open source?

No open-source release is listed for Commerce Layer API + MCP. Vendure is open source (GPL-3.0-or-later).

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