Head to head · Commerce catalogues · October 2026 research run

Snipcart API + MCP vs Vendure

Vendure scores 72.3 (BB) on agent readiness against Snipcart API + MCP's 47.2 (D), and leads in every scored category. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

Snipcart API + MCP D

Best for Static-site merchants who want an agent to handle orders, refunds and coupons.

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Vendure loses 6 points for them

Watch for

No server-side cart or checkout. Orders only come from the browser widget

Vendure BB

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

Ahead on

  • Reliability, 89 against 68
  • Schema & documentation, 91 against 51
  • Agent ergonomics, 68 against 40
  • Security & auth, 65 against 20
  • Payments & pricing, 75 against 53
  • Maintenance & community, 85 against 38
  • Transparency & trust, 74 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 3.0 against 1.5 out of 5

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.

Maintenance & community Vendure +47

Snipcart API + MCP 38

Release notes on 24 September 2026, 47 days before the check (20). Four dated entries since 12 August, but only 26 August (creditNoteNumber added to refunds in the API) and 24 September (an invoice-number fix, with shipping boxes and dashboard analytics) touch what the API serves. 9 September (discounts page, crawler TLS) and 21 September (refund email templates) are about the hosted app and dashboard, so two count and the line needs three (0). Public release notes and a support forum the status page monitors (12). No official API SDK, and the MCP server isn't in the official registry (3). The MCP source isn't public, so its CI can't be seen (3). 20 + 0 + 12 + 3 + 3 = 38.

Vendure 85

v3.8.1 tagged on 23 October 2026, 9 days before this check (30). v3.7.2 on 3 August, v3.7.3 on 1 September, v3.7.4 on 5 October, v3.8.0 on 12 October and v3.8.1 on 23 October (20). 170 open issues per the 1 October check, many filed by maintainers themselves; GitHub's issue pages refused us on 1 November (17). No official client SDK. The MCP plugin and its SDK shipped in 3.8.0 (8). CI workflows for build and test, floating dependencies and dependency impact still in the repository (10). 30+20+17+8+10 = 85.

Security & auth Vendure +45

Snipcart API + MCP 20

One secret key per mode (test or live) with full account access, sent as Basic auth or, for the MCP, in an X-Snipcart-Api-Key header. The MCP docs say OAuth 2.1 isn't supported (12). No scoped or read-only keys, and refund, stock, archive and delete tools carry no documented confirmation, though the tools reference marks refunds and customer deletion irreversible (3). Tools return customer and order data, with no prompt-injection guidance found (5). Order logs are notes, not an audit trail (0). No security.txt per the 30 September check, and no disclosure contact in the terms. The security page says Snipcart is hosted to PCI compliance specifications, with no attestation or reporting route (0). Total 20.

Vendure 65

API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a vendure-api-key header. Since 3.7.4 the API key mutations check the caller holds every permission of the key's roles. No OAuth in the GraphQL APIs; the MCP plugin uses OAuth 2.1 (28). Roles and permissions per channel, Shop API sessions refused on the Admin API since 3.8.0, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). The MCP plugin released in 3.8.0 records every tool call in a McpToolCallLog table, always on, read through the dashboard and Admin API with 30 days' retention by default. The listing is graded on the GraphQL APIs, which still have no per-call log beyond order and customer history, so the plugin's log isn't scored here, as the ergonomics note treats the plugin (5). SECURITY.md takes private reports through GitHub and supports only the latest 3.x minor. Advisories are published with each release, 11 in 3.7.3, two in 3.7.4, one in 3.8.0 and three in 3.8.1. No security.txt (404), bounty or certification found (13). 28+14+5+5+13 = 65.

Schema & documentation Vendure +40

Snipcart API + MCP 51

No OpenAPI file, and the MCP source isn't public, so JSON Schema for the tools couldn't be read (5). No llms.txt (docs.snipcart.com/llms.txt answered 404 on 10 November) (0). The MCP tools reference documents all 38 tools, each with its purpose and what it returns, and marks irreversible and failing cases (refunds, customer deletion, used discounts), with no when-not-to-use guidance (12). Its parameter tables give a type, a required flag and a description for every input, with allowed status values listed in the descriptions, while addresses and metadata are free-form objects (10). The REST reference has examples per endpoint, and an Errors page lists status codes and the 400 error payload, with an MCP error-handling page giving causes and fixes (12). Dated release notes every few weeks and a stated change policy, new fields may appear without notice but existing ones aren't renamed or removed (12). 5 + 0 + 12 + 10 + 12 + 12 = 51.

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

Agent ergonomics Vendure +28

Snipcart API + MCP 40

38 MCP tools with no toolsets or filtering (5). list_orders, list_customers and list_products take limit and offset (default 20) with status or date filters, and abandoned carts use a continuation token, but list_discounts, get_customer_orders and the refund and notification lists take no paging (10, an earlier partial held). Errors are documented for both surfaces, REST status codes with a per-parameter 400 payload, and MCP errors with their cause and fix (20). No idempotency keys and no readOnlyHint or destructiveHint annotations documented, though the tools create refunds, delete customers and archive products (0). No official API SDK. Setup in Claude Code is one line (5). 5 + 10 + 20 + 0 + 5 = 40.

Vendure 68

GraphQL field selection sizes every response (23). List queries take take, skip, filter and sort (20). ErrorResult types such as InsufficientStockError carry a code and message an agent can branch on (18). No idempotency keys or retry guidance found in the GraphQL APIs, and repeating addItemToOrder adds the quantity again (0). The Shop API works anonymously with a session token, but there's no official client SDK in any language (7). The MCP plugin released in 3.8.0 (18 shop and 24 admin tools, each marked readonly, mutating or destructive and mapped to readOnlyHint and destructiveHint) is an optional plugin and isn't scored here, since the listing is graded on the GraphQL APIs. 23+20+18+0+7 = 68.

Payments & pricing Vendure +22

Snipcart API + MCP 53

No x402, MPP or L402 (0). Public pricing, 2 per cent of sales, or $20 a month for stores under $1,000 in monthly sales, which is per-sale rather than per-call (15). Test mode is free with no card (20). A person signs up in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

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.

Reliability Vendure +21

Snipcart API + MCP 68

status.snipcart.com runs Upptime from the public snipcart/status repository, checking four URLs, the merchant dashboard host (app.snipcart.com, which also serves the API), the website, the docs and the support forum. Neither the API path nor the MCP endpoint at ai.snipcart.com is checked on its own (15). Since 12 August the repository's history records no downtime on the dashboard host, and the docs went down twice, on 21 and 24 September (25, an earlier partial held). REST rate limits aren't published beyond per-endpoint limits on discount listing and order notifications. The MCP error-handling page gives 100 requests a minute and 10 concurrent per key, plus per-tool limits (8, an earlier partial held). The same page says an exceeded limit returns 429 with a retryAfter value, the concurrency limit returns 503 to be retried after a pause, and the server retries Snipcart API 429s twice with exponential backoff. Nothing on idempotency or safe retries for writes (10). No SLA in the terms (0). The REST API and MCP server are both live, not beta (10). 15 + 25 + 8 + 10 + 0 + 10 = 68.

Vendure 89

Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.

Score by category

CategoryWeightSnipcart API + MCPVendureEdge
Reliability16%6889Vendure +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5191Vendure +40
Agent ergonomics13%4068Vendure +28
Security & auth14%2065Vendure +45
Payments & pricing10%5375Vendure +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3885Vendure +47
Transparency & trust7%6174Vendure +13
Negative events≤150-6
TotalD 47.2/100BB 72.3/100

Facts side by side

FactSnipcart API + MCPVendure
KindHTTP APIHTTP API
VendorSnipcart (Duda)Vendure (Elevantiq GmbH)
Hosted endpointhttps://app.snipcart.com/apihttps://readonlydemo.vendure.io/shop-api
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneGPL-3.0-or-later
Tools exposed38none
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-09-242026-10-23
Terms last updatedno date givennot 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 benchmarkingnot found in the textnot 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
Popularitynone8.5k stars, 30k npm/wk
Agent reviews1.5/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Vendure 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

Snipcart API + MCP

Hosted MCP server with 38 documented tools and a self-hostable Bun build. No server-side cart or checkout. Orders only come from the browser widget.

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

Snipcart API + MCP

  1. Use the agent for back-office jobs (orders, refunds, discounts, stock, abandoned carts), not for placing orders
  2. Start with a test-mode key (ST_ prefix) before switching to live (SL_)
  3. Send the key in X-Snipcart-Api-Key. OAuth-only clients can't connect
  4. Stay under 100 MCP requests a minute and 10 in flight per key. On 429, wait for retryAfter; on 503, pause and retry
  5. Ignore unknown response fields. Snipcart adds fields without a new version
  6. Page list_orders, list_customers and list_products with limit and offset (default 20); abandoned carts use a continuation token

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, Snipcart API + MCP or Vendure?

Vendure scores 72.3 (BB) on agent readiness against Snipcart API + MCP's 47.2 (D), and leads in every scored category.

Do Snipcart API + MCP and Vendure need an API key?

Snipcart API + MCP needs an API key. Vendure takes an API key or an OAuth sign-in.

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

Yes. Snipcart API + MCP has a hosted endpoint at https://app.snipcart.com/api and Vendure at https://readonlydemo.vendure.io/shop-api.

Are Snipcart API + MCP and Vendure open source?

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

Other comparisons with Snipcart 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.