{ "data": { "a": { "slug": "commercetools", "name": "commercetools", "vendor": "commercetools GmbH", "vendorUrl": "https://commercetools.com", "kind": "http-api", "category": "commerce", "summary": "Headless commerce platform from commercetools GmbH in Munich, with HTTP and GraphQL APIs for catalogue, carts, checkout, orders and customers. Agents reach it through the API, four SDKs or a managed MCP server per project.", "url": "https://www.anchorterminal.com/tools/commercetools", "markdownUrl": "https://www.anchorterminal.com/tools/commercetools.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/commercetools.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/commercetools.json", "repo": "https://github.com/commercetools/commercetools-api-reference", "license": "Proprietary 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", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.{region}.commercetools.com/{projectKey}", "packages": [ { "registry": "npm", "name": "@commercetools/platform-sdk" }, { "registry": "npm", "name": "@commercetools/commerce-mcp" } ], "auth": "oauth", "authNotes": "OAuth 2.0. A person creates an API Client in the Merchant Centre (or through the API Clients API) with chosen scopes, and the secret is shown once. The client credentials flow at https://auth.{region}.commercetools.com/oauth/token returns a Bearer token valid for 48 hours by default. Scopes are view or manage per resource and per store, and `manage_project` grants everything. Password, anonymous-session and refresh flows exist for shoppers. A managed MCP server takes a token scoped to `mcp:{projectKey}:{mcpServerKey}` (30 days at most), OAuth client credentials discovery, or a browser sign-in with an Identity account. Access is self-serve through the trial sign-up form.", "pricing": "paid", "pricingNotes": "No public prices. The pricing page describes order-based pricing and sends buyers to sales, and the product is also sold through the AWS and Google Cloud marketplaces. A 60-day trial has every core commerce API and the Merchant Centre, needs no card and does not convert automatically, so an agent can start without a contract. InStore, Frontend and the agent products are not in the trial (https://commercetools.com/free-trial, checked 2026-10-08).", "priceSummary": "Paid", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 221261, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.commercetools.com/api/", "llmsTxt": "https://docs.commercetools.com/llms.txt", "openapi": "https://raw.githubusercontent.com/commercetools/commercetools-api-reference/main/oas/api/openapi.yaml", "capabilities": [ "commerce.products", "commerce.cart", "commerce.checkout", "commerce.orders", "commerce.headless" ], "tags": [ "hosted", "enterprise", "closed-source", "mcp", "oauth", "openapi", "graphql", "llms-txt", "typescript", "java", "php", "dotnet", "webhooks", "sales-led", "status-page", "sla", "soc2" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 133, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 85, "payments": 20, "reliability": 73, "schema": 86, "security": 70, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.", "strengths": [ "Public OpenAPI 3.0 file with 822 operations, plus RAML, a GraphQL schema, llms.txt and Markdown copies of every docs page", "OAuth 2.0 API Clients with view and manage scopes per resource, a token revocation endpoint, and no tokens accepted in URL parameters", "Managed MCP server per agent with a chosen tool list, field filtering and redaction, and readOnlyHint and destructiveHint on every tool since 1 October 2026", "99.9 per cent monthly availability SLA with service credits, published in the docs", "60-day trial with every core commerce API and no card" ], "weaknesses": [ "No public price. The pricing page describes order-based pricing and sends buyers to sales", "The docs state that the HTTP API has no single documented platform-wide rate limit", "Managed MCP Servers, AI Hub and Platform Insights are excluded from the standard SLA", "API-wide change tracking needs the paid Audit Log Premium add-on. Audit Log Basic records Merchant Centre changes only", "No security.txt and no bug bounty found, and audit reports are released under NDA" ], "agentNotes": [ "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", "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", "Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body", "For MCP, ask for an API Client scoped to `mcp:{projectKey}:{mcpServerKey}` and a server limited to the tools the task needs, not `all`", "Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.3 } ], "editorialScores": { "ergonomics": 83, "maintenance": 85, "payments": 20, "reliability": 73, "schema": 86, "security": 70, "transparency": 75 }, "provenanceScore": 86 }, "connect": { "install": "npm install @commercetools/platform-sdk", "http": "curl https://{auth_host}/oauth/token -X POST \\\n --basic --user \"{clientId}:{clientSecret}\" \\\n -d \"grant_type=client_credentials\u0026scope=manage_project:{projectKey}\"\ncurl https://api.{region}.commercetools.com/{projectKey}/ \\\n -X GET \\\n -H \"Authorization: Bearer ${BEARER_TOKEN}\"", "config": { "mcpServers": { "managed-mcp-servers": { "headers": { "Authorization": "Bearer \u003cyour-ctp-token\u003e" }, "type": "http", "url": "\u003cyour-mcp-server-url\u003e" } } } }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/commercetools" }, "area": "business", "provenance": { "legalEntity": "commercetools GmbH", "domain": "commercetools.com", "domainRegistered": "2002-05-13", "endpointOnVendorDomain": true, "terms": "https://commercetools.com/msa", "privacy": "https://commercetools.com/privacy", "statusPage": "https://status.commercetools.com", "changelog": "https://docs.commercetools.com/docs/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The imprint names commercetools GmbH, Adams-Lehmann-Str. 44, 80797 Munich, Amtsgericht München HRB 161496.", "The Master Service Agreement at commercetools.com/msa governs paid use once an Order Form is signed. Trial use falls under the 60 Days Trial Agreement at commercetools.com/trial-agreement, last updated 24 July 2024.", "The privacy notice covers the websites in section III and customers' use of the service in section IV. Data that customers store in the platform falls under the DPA at commercetools.com/dpa, last updated 1 October 2024.", "commercetools.com/.well-known/security.txt and docs.commercetools.com/.well-known/security.txt both return 404.", "API, auth and MCP hosts are subdomains of commercetools.com for each region. RDAP gives a registration date of 2002-05-13 for commercetools.com." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/commercetools.json", "live": { "slug": "commercetools", "probe": { "target": "https://api.{region}.commercetools.com/{projectKey}", "method": "get", "lastAt": "2026-10-10T01:37:48.433908159Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 250, "samples30d": 337, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 0 }, { "date": "2026-10-09", "probes": 250, "ok": 0 }, { "date": "2026-10-10", "probes": 17, "ok": 0 } ], "outages": [ { "start": "2026-10-08T17:31:33.341731081Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "vendorStatus": { "page": "https://status.commercetools.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:22.815951892Z" }, "versions": [ { "registry": "npm", "name": "@commercetools/commerce-mcp", "version": "4.2.2", "seenAt": "2026-10-09T16:47:05.47069042Z" }, { "registry": "npm", "name": "@commercetools/platform-sdk", "version": "9.6.0", "seenAt": "2026-10-09T16:47:03.497981846Z" } ], "githubStars": 66, "npmWeekly": 168765, "securityTxt": { "url": "https://commercetools.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:59.776364005Z" }, "llmsTxt": { "url": "https://docs.commercetools.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:42.939911287Z" }, "pages": [ { "url": "https://docs.commercetools.com/docs/release-notes", "kind": "changelog", "status": 404, "checkedAt": "2026-10-09T18:36:59.884324341Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://commercetools.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:34:15.906943303Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "58be3463d4f5" }, { "url": "https://commercetools.com/msa", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:34:13.727569887Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c72525a36335" } ], "updatedAt": "2026-10-10T01:37:48.433908159Z" } }, "answer": "commercetools and Spree Commerce score within a point of each other on agent readiness, 71.3 (BB) and 70.4 (BB). Spree Commerce leads on reliability, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "spree-commerce", "name": "Spree Commerce", "vendor": "Vendo Connect Inc", "vendorUrl": "https://spreecommerce.org", "kind": "http-api", "category": "commerce", "summary": "Spree Commerce is an open-source commerce platform on Ruby on Rails, maintained by Vendo Connect Inc. A self-hosted store runs a Store API for catalogue, cart and checkout, and an Admin API for back-office work.", "url": "https://www.anchorterminal.com/tools/spree-commerce", "markdownUrl": "https://www.anchorterminal.com/tools/spree-commerce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/spree-commerce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/spree-commerce.json", "repo": "https://github.com/spree/spree", "license": "BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@spree/sdk" }, { "registry": "npm", "name": "@spree/cli" }, { "registry": "npm", "name": "@spree/admin-sdk" }, { "registry": "rubygems", "name": "spree" } ], "auth": "mixed", "authNotes": "Store API calls need a publishable key (`pk_`) in the `X-Spree-Api-Key` header, plus a customer JWT as a Bearer token or a cart token in `X-Spree-Token` for guests. Admin API calls take a secret key (`sk_`) with `read_*` and `write_*` scopes per resource, or an admin JWT. Keys are created by the store's operator in the dashboard or with `spree api-key create`, with no vendor approval.", "pricing": "freemium", "pricingNotes": "Free to self-host under BSD 3-Clause, with no platform or transaction fee. The Enterprise Edition is custom pricing through sales. A free hosted Sandbox lets an agent's owner try the Admin API without a contract, for evaluation with test data only (https://spreecommerce.org/enterprise/, checked 2026-10-09).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI files or the repository (checked 2026-10-09). Payments go through provider integrations such as Stripe, Adyen and PayPal.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 15750, "npmWeekly": 1576, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://spreecommerce.org/docs", "llmsTxt": "https://spreecommerce.org/docs/llms.txt", "openapi": "https://spreecommerce.org/docs/api-reference/store.yaml", "capabilities": [ "commerce.products", "commerce.cart", "commerce.checkout", "commerce.orders", "commerce.headless" ], "tags": [ "open-source", "self-hosted", "local", "openapi", "llms-txt", "mcp", "typescript", "ruby", "webhooks", "freemium" ], "lastRelease": "2026-07-28", "graded": true, "anchor": { "graded": true, "score": 70.4, "grade": "BB", "agentReady": true, "rank": 155, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 90, "maintenance": 81, "payments": 55, "reliability": 82, "schema": 85, "security": 65, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "2026-07-20: six security advisories were published for `spree_api` and related gems between 8 January and 20 July 2026, four rated High, among them guest address and order disclosure without authentication (GHSA-87fh-rc96-6fr6, GHSA-p6pv-q7rc-g4h9, 5 February) and a guest cart takeover on `PATCH /api/v3/store/carts/:id/associate` (GHSA-4825-p4xm-pcf2, 20 July, fixed in 5.4.4 and 5.5.4). All are published with patched versions, so the deduction is reduced (https://github.com/spree/spree/security/advisories)." ], "verdict": "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.", "bestFor": "Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.", "strengths": [ "OpenAPI 3.0.3 files for the Store API (81 paths, 99 operations) and Admin API (259 paths, 417 operations), plus llms.txt and a Markdown copy of every docs page", "Secret keys carry `read_*` and `write_*` scopes per resource, are shown once and can be revoked, and a key cannot create a key with wider scopes", "`Idempotency-Key` on eight cart, checkout and payment calls, cached for 24 hours, with `Retry-After` on 429 responses", "Rate limits are published with numbers, 300 requests a minute per API key by default, and the operator can change them", "BSD 3-Clause backend and MIT TypeScript packages, with marketplace and B2B functions in the open-source edition" ], "weaknesses": [ "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", "The default docs and the main-branch OpenAPI files describe 6.0, a release candidate dated 8 October 2026. The stable release is 5.6.1 of 28 July 2026", "The audit trail is in the paid Enterprise Edition only, and Enterprise prices are not published", "Supported-version end dates differ between `SECURITY.md` (5.x until 26 March 2027) and the docs security policy (5.0 until 26 March 2028)", "The official MCP server searches and reads the docs only. Store and admin MCP servers are open roadmap issues" ], "agentNotes": [ "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", "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", "Ask for `fields` and `expand` explicitly. Relations are left out by default and `limit` stops at 100", "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", "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" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.4 } ], "editorialScores": { "ergonomics": 90, "maintenance": 81, "payments": 55, "reliability": 82, "schema": 85, "security": 65, "transparency": 75 }, "provenanceScore": 45 }, "connect": { "install": "npx create-spree-app@latest my-store", "http": "curl -X GET 'http://localhost:3000/api/v3/store/products' -H 'X-Spree-Api-Key: pk_xxx'", "claudeCode": "claude mcp add --transport http spree-docs https://spreecommerce.org/docs/mcp", "config": { "mcpServers": { "spree-docs": { "url": "https://spreecommerce.org/docs/mcp" } } } }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/spree-commerce" }, "area": "business", "unitPrices": [ { "item": "Community Edition, self-hosted", "unit": "month", "usd": 0, "note": "BSD 3-Clause, the operator pays for its own servers" } ], "provenance": { "legalEntity": "Vendo Connect Inc", "domain": "spreecommerce.org", "domainRegistered": "2009-04-03", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/spree/spree/releases", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Sandbox terms name VENDO CONNECT INC, a Delaware corporation (file number 7005612), 3500 S DuPont Highway, Dover, Delaware 19901, as the company behind the Spree Commerce project. The `LICENSE` file also names Vendo Sp. z o.o. as a copyright holder.", "The API runs on the operator's own server, so there is no vendor endpoint and no vendor status page.", "No terms or privacy document governs the self-hosted software, and the BSD 3-Clause licence stands in. The published terms (https://spreecommerce.org/terms-of-service/) and privacy notice (https://spreecommerce.org/privacy-policy-sandbox/), both dated 10 July 2026, cover only the hosted Sandbox and Vendo's websites.", "https://spreecommerce.org/.well-known/security.txt returns 404. `SECURITY.md` in the repository gives a security mailbox for reports.", "RDAP for spreecommerce.org gives a registration date of 2009-04-03 and GoDaddy.com, LLC as registrar." ], "score": 45 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/spree-commerce.json", "live": { "slug": "spree-commerce", "versions": [ { "registry": "github", "name": "spree/spree", "version": "v5.6.1", "released": "2026-07-28", "seenAt": "2026-10-09T17:21:34.764539584Z" }, { "registry": "npm", "name": "@spree/admin-sdk", "version": "0.1.0", "seenAt": "2026-10-09T17:21:32.71633834Z" }, { "registry": "npm", "name": "@spree/cli", "version": "3.2.2", "seenAt": "2026-10-09T17:21:30.96599442Z" }, { "registry": "npm", "name": "@spree/sdk", "version": "1.2.1", "seenAt": "2026-10-09T17:21:28.899108995Z" } ], "githubStars": 15751, "npmWeekly": 1576, "updatedAt": "2026-10-09T17:21:34.764539584Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "commercetools GmbH", "b": "Vendo Connect Inc", "name": "Vendor" }, { "a": "https://api.{region}.commercetools.com/{projectKey}", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary 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", "b": "BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-07-28", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "221k npm/wk", "b": "16k stars, 1.6k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "commercetools and Spree Commerce score within a point of each other on agent readiness, 71.3 (BB) and 70.4 (BB). Spree Commerce leads on reliability, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, commercetools or Spree Commerce?" }, { "answer": "commercetools uses an OAuth sign-in. Spree Commerce takes an API key or an OAuth sign-in.", "question": "Do commercetools and Spree Commerce need an API key?" }, { "answer": "commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey}. No hosted endpoint is listed for Spree Commerce.", "question": "Can an agent call commercetools and Spree Commerce without installing anything?" }, { "answer": "No open-source release is listed for commercetools. 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).", "question": "Are commercetools and Spree Commerce open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 70 against 65", "Transparency \u0026 trust, 81 against 60" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine", "No incidents deducted, where Spree Commerce loses 5 points for them" ], "goodFor": "Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.", "slug": "commercetools", "watchFor": "No public price. The pricing page describes order-based pricing and sends buyers to sales" }, { "aheadOn": [ "Reliability, 82 against 73", "Agent ergonomics, 90 against 83", "Payments \u0026 pricing, 55 against 20" ], "also": [ "Open source" ], "goodFor": "Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.", "slug": "spree-commerce", "watchFor": "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" } ], "job": { "capability": "commerce.products", "name": "Commerce catalogues" }, "others": [ { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-commercetools.json", "title": "Adobe Commerce (Magento) vs commercetools", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-commercetools" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.json", "title": "Adobe Commerce (Magento) vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/bigcommerce-vs-commercetools.json", "title": "BigCommerce API + MCP vs commercetools", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-commercetools" }, { "json": "https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.json", "title": "BigCommerce API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/commerce-layer-vs-commercetools.json", "title": "Commerce Layer API + MCP vs commercetools", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-commercetools" }, { "json": "https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.json", "title": "Commerce Layer API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-ecwid.json", "title": "commercetools vs Ecwid by Lightspeed", "url": "https://www.anchorterminal.com/compare/commercetools-vs-ecwid" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-elastic-path.json", "title": "commercetools vs Elastic Path API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-elastic-path" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-medusa.json", "title": "commercetools vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-saleor.json", "title": "commercetools vs Saleor API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-saleor" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-shopify.json", "title": "commercetools vs Shopify API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-shopify" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-shopware.json", "title": "commercetools vs Shopware", "url": "https://www.anchorterminal.com/compare/commercetools-vs-shopware" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-snipcart.json", "title": "commercetools vs Snipcart API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-snipcart" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-square.json", "title": "commercetools vs Square", "url": "https://www.anchorterminal.com/compare/commercetools-vs-square" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-swell.json", "title": "commercetools vs Swell", "url": "https://www.anchorterminal.com/compare/commercetools-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-vendure.json", "title": "commercetools vs Vendure", "url": "https://www.anchorterminal.com/compare/commercetools-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-wix.json", "title": "commercetools vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/commercetools-vs-wix" }, { "json": "https://www.anchorterminal.com/compare/commercetools-vs-woocommerce.json", "title": "commercetools vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/commercetools-vs-woocommerce" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.json", "title": "Ecwid by Lightspeed vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.json", "title": "Elastic Path API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.json", "title": "Medusa API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/medusa-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.json", "title": "Saleor API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/saleor-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.json", "title": "Shopify API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/shopify-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.json", "title": "Shopware vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/shopware-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.json", "title": "Snipcart API + MCP vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-square.json", "title": "Spree Commerce vs Square", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-square" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-swell.json", "title": "Spree Commerce vs Swell", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.json", "title": "Spree Commerce vs Vendure", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-wix.json", "title": "Spree Commerce vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-wix" }, { "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.json", "title": "Spree Commerce vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce" } ], "scores": [ { "by": 9, "commercetools": 73, "edge": "spree-commerce", "key": "reliability", "name": "Reliability", "spree-commerce": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "commercetools": 86, "edge": "commercetools", "key": "schema", "name": "Schema \u0026 documentation", "spree-commerce": 85, "weight": 13 }, { "by": 7, "commercetools": 83, "edge": "spree-commerce", "key": "ergonomics", "name": "Agent ergonomics", "spree-commerce": 90, "weight": 13 }, { "by": 5, "commercetools": 70, "edge": "commercetools", "key": "security", "name": "Security \u0026 auth", "spree-commerce": 65, "weight": 14 }, { "by": 35, "commercetools": 20, "edge": "spree-commerce", "key": "payments", "name": "Payments \u0026 pricing", "spree-commerce": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "commercetools": 85, "edge": "commercetools", "key": "maintenance", "name": "Maintenance \u0026 community", "spree-commerce": 81, "weight": 7 }, { "by": 21, "commercetools": 81, "edge": "commercetools", "key": "transparency", "name": "Transparency \u0026 trust", "spree-commerce": 60, "weight": 7 } ], "summary": "commercetools and Spree Commerce score within a point of each other on agent readiness, 71.3 (BB) and 70.4 (BB). Spree Commerce leads on reliability, agent ergonomics and payments \u0026 pricing. Both do commerce catalogues.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce", "json": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.md", "slim": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.min.md" }, "markdown": "commercetools and Spree Commerce score within a point of each other on agent readiness, 71.3 (BB) and 70.4 (BB). Spree Commerce leads on reliability, agent ergonomics and payments \u0026 pricing. Both do commerce catalogues.\n\n- commercetools: grade BB, 71.3/100, rank #133 of 950. Markdown https://www.anchorterminal.com/tools/commercetools.md · JSON https://www.anchorterminal.com/api/v1/tools/commercetools.json\n- Spree Commerce: grade BB, 70.4/100, rank #155 of 950. Markdown https://www.anchorterminal.com/tools/spree-commerce.md · JSON https://www.anchorterminal.com/api/v1/tools/spree-commerce.json\n- Best commerce platforms and checkout APIs for AI agents: https://www.anchorterminal.com/best/commerce/index.md\n- All 136 commerce comparisons: https://www.anchorterminal.com/compare/commerce/index.md\n\n## Which one, for what\n\n### commercetools (BB)\n\nGood for: Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.\n\nAhead on:\n- Security \u0026 auth, 70 against 65\n- Transparency \u0026 trust, 81 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- No incidents deducted, where Spree Commerce loses 5 points for them\n\nWatch for: No public price. The pricing page describes order-based pricing and sends buyers to sales\n\n### Spree Commerce (BB)\n\nGood for: Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.\n\nAhead on:\n- Reliability, 82 against 73\n- Agent ergonomics, 90 against 83\n- Payments \u0026 pricing, 55 against 20\n\nAlso in its favour:\n- Open source\n\nWatch 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\n\n\n## Score by category\n\n| Category | Weight | commercetools | Spree Commerce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 82 | Spree Commerce +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 85 | commercetools +1 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 90 | Spree Commerce +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 65 | commercetools +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 55 | Spree Commerce +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 81 | commercetools +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 60 | commercetools +21 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **71.3 · BB** | **70.4 · BB** | |\n\n## Facts side by side\n\n| Fact | commercetools | Spree Commerce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | commercetools GmbH | Vendo Connect Inc |\n| Hosted endpoint | `https://api.{region}.commercetools.com/{projectKey}` | no (local only) |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary 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 | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-07-28 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 221k npm/wk | 16k stars, 1.6k npm/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### commercetools\n\n1. 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\n2. 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\n3. Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body\n4. For MCP, ask for an API Client scoped to `mcp:{projectKey}:{mcpServerKey}` and a server limited to the tools the task needs, not `all`\n5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request\n\n### Spree Commerce\n\n1. 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\n2. 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\n3. Ask for `fields` and `expand` explicitly. Relations are left out by default and `limit` stops at 100\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, commercetools or Spree Commerce?\n\ncommercetools and Spree Commerce score within a point of each other on agent readiness, 71.3 (BB) and 70.4 (BB). Spree Commerce leads on reliability, agent ergonomics and payments \u0026 pricing.\n\n### Do commercetools and Spree Commerce need an API key?\n\ncommercetools uses an OAuth sign-in. Spree Commerce takes an API key or an OAuth sign-in.\n\n### Can an agent call commercetools and Spree Commerce without installing anything?\n\ncommercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey}. No hosted endpoint is listed for Spree Commerce.\n\n### Are commercetools and Spree Commerce open source?\n\nNo open-source release is listed for commercetools. 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).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"commercetools\", \"b\": \"spree-commerce\"}`. From a terminal: `anchor compare commercetools spree-commerce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/commercetools.json and https://www.anchorterminal.com/api/v1/tools/spree-commerce.json\n\n## Other comparisons with commercetools or Spree Commerce\n\n- [Adobe Commerce (Magento) vs commercetools](https://www.anchorterminal.com/compare/adobe-commerce-vs-commercetools.md)\n- [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md)\n- [BigCommerce API + MCP vs commercetools](https://www.anchorterminal.com/compare/bigcommerce-vs-commercetools.md)\n- [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md)\n- [Commerce Layer API + MCP vs commercetools](https://www.anchorterminal.com/compare/commerce-layer-vs-commercetools.md)\n- [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md)\n- [commercetools vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/commercetools-vs-ecwid.md)\n- [commercetools vs Elastic Path API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-elastic-path.md)\n- [commercetools vs Medusa API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-medusa.md)\n- [commercetools vs Saleor API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-saleor.md)\n- [commercetools vs Shopify API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-shopify.md)\n- [commercetools vs Shopware](https://www.anchorterminal.com/compare/commercetools-vs-shopware.md)\n- [commercetools vs Snipcart API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-snipcart.md)\n- [commercetools vs Square](https://www.anchorterminal.com/compare/commercetools-vs-square.md)\n- [commercetools vs Swell](https://www.anchorterminal.com/compare/commercetools-vs-swell.md)\n- [commercetools vs Vendure](https://www.anchorterminal.com/compare/commercetools-vs-vendure.md)\n- [commercetools vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/commercetools-vs-wix.md)\n- [commercetools vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/commercetools-vs-woocommerce.md)\n- [Ecwid by Lightspeed vs Spree Commerce](https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.md)\n- [Elastic Path API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.md)\n- [Medusa API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md)\n- [Saleor API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.md)\n- [Shopify API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.md)\n- [Shopware vs Spree Commerce](https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.md)\n- [Snipcart API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.md)\n- [Spree Commerce vs Square](https://www.anchorterminal.com/compare/spree-commerce-vs-square.md)\n- [Spree Commerce vs Swell](https://www.anchorterminal.com/compare/spree-commerce-vs-swell.md)\n- [Spree Commerce vs Vendure](https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.md)\n- [Spree Commerce vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/spree-commerce-vs-wix.md)\n- [Spree Commerce vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "commercetools vs Spree Commerce", "url": "" } ], "description": "commercetools and Spree Commerce score within a point of each other for commerce catalogues, 71.3 and 70.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "commercetools BB 71.3", "Spree Commerce BB 70.4", "scores" ], "h1": "commercetools vs Spree Commerce", "image": "https://www.anchorterminal.com/assets/og/compare-commercetools-vs-spree-commerce.png", "path": "/compare/commercetools-vs-spree-commerce", "published": "2026-10-01", "section": "tools", "title": "commercetools vs Spree Commerce for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce" }, "tokens": { "markdown": 2950, "slim": 780 }, "version": 1 }