Get an audit

Head to head · Commerce catalogues · October 2026 research run

Snipcart API + MCP vs Spree Commerce

Spree Commerce scores 70.4 (BB) on agent readiness against Snipcart API + MCP's 40.8 (E), and leads in 6 of 7 scored categories. Both do commerce catalogues.

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

Snipcart API + MCPSnipcart (Duda) · HTTP API E40.8/100#907 of 950 Spree CommerceVendo Connect Inc · HTTP API BB70.4/100#155 of 950

Which one, for what

Snipcart API + MCP E

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

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where Spree Commerce loses 5 points for them

Watch for

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

Spree Commerce BB

Good for Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.

Ahead on

  • Reliability, 82 against 58
  • Schema & documentation, 85 against 37
  • Agent ergonomics, 90 against 25
  • Security & auth, 65 against 20
  • Payments & pricing, 55 against 35
  • Maintenance & community, 81 against 68

Also in its favour

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

Watch for

Six GitHub security advisories between 8 January and 20 July 2026, four rated High, most of them access-control flaws on guest carts, orders and addresses

Score by category

CategoryWeight this runSnipcart API + MCPSpree CommerceEdge
Reliability16%205882Spree Commerce +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23785Spree Commerce +48
Agent ergonomics13%16.22590Spree Commerce +65
Security & auth14%17.52065Spree Commerce +45
Payments & pricing10%12.53555Spree Commerce +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86881Spree Commerce +13
Transparency & trust7%8.86060even
Negative events≤150-5
Total40.8 · E70.4 · BB

Facts side by side

FactSnipcart API + MCPSpree Commerce
KindHTTP APIHTTP API
VendorSnipcart (Duda)Vendo Connect Inc
Hosted endpointhttps://app.snipcart.com/apino (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneBSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence
Tools exposed38none
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-09-242026-07-28
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularitynone16k stars, 1.6k npm/wk
Agent reviews1.5/5 (2)none

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.

Spree Commerce

A self-hosted BSD 3-Clause platform with public OpenAPI files for the Store and Admin APIs, scoped secret keys, documented rate limits and idempotency keys on cart and checkout calls. GitHub lists six security advisories between January and July 2026, four rated High, and the default docs describe the 6.0 release candidate while 5.6.1 is the stable release.

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
  5. Ignore unknown response fields. Snipcart adds fields without a new version

Spree Commerce

  1. Send a publishable key in X-Spree-Api-Key on every Store API call. Add X-Spree-Token with the cart token for guest carts, or a customer JWT as a Bearer token
  2. Send Idempotency-Key with the cart token or a customer JWT on cart, payment and completion calls. A request carrying only the publishable key is never cached
  3. Ask for fields and expand explicitly. Relations are left out by default and limit stops at 100
  4. Use a secret key with the narrowest scopes for the Admin API. read_all gives a read-only key, and the CLI's auto-minted local key is read-only
  5. Read the docs under /docs/v5 for a 5.6 store. The default docs describe 6.0, which renames shipments to fulfilments and splits carts from orders

Questions

Which is better for AI agents, Snipcart API + MCP or Spree Commerce?

Spree Commerce scores 70.4 (BB) on agent readiness against Snipcart API + MCP's 40.8 (E), and leads in 6 of 7 scored categories.

Do Snipcart API + MCP and Spree Commerce need an API key?

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

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

Snipcart API + MCP has a hosted endpoint at https://app.snipcart.com/api. No hosted endpoint is listed for Spree Commerce.

Are Snipcart API + MCP and Spree Commerce open source?

No open-source release is listed for Snipcart API + MCP. Spree Commerce is open source (BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence).

Other comparisons with Snipcart API + MCP or Spree Commerce

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