{ "data": { "a": { "slug": "adobe-commerce", "name": "Adobe Commerce (Magento)", "vendor": "Adobe Inc.", "vendorUrl": "https://business.adobe.com/products/commerce.html", "kind": "http-api", "category": "commerce", "summary": "Commerce platform from Adobe, built on the open-source Magento core. It runs as Adobe Commerce as a Cloud Service, on Adobe's cloud infrastructure or on the merchant's own servers, and agents reach a store through its REST and GraphQL APIs.", "url": "https://www.anchorterminal.com/tools/adobe-commerce", "markdownUrl": "https://www.anchorterminal.com/tools/adobe-commerce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/adobe-commerce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/adobe-commerce.json", "repo": "https://github.com/magento/magento2", "license": "Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@adobe/aio-commerce-sdk" } ], "auth": "mixed", "authNotes": "Access comes from the merchant, with no Adobe review of the caller. On Adobe Commerce as a Cloud Service an organisation admin creates an OAuth credential in Adobe Developer Console, and calls carry an Adobe IMS bearer token, from client credentials with the `commerce.accs` scope or from a user flow tied to an Admin role. On Adobe Commerce on Cloud, on-premises and Magento Open Source, the merchant creates an integration limited to chosen ACL resources and requests are signed by OAuth 1.0a. Admin tokens last 4 hours and customer tokens 1 hour by default, and a bare integration token as a bearer token is off by default.", "pricing": "freemium", "pricingNotes": "No price was read. business.adobe.com timed out on every request on 8 October 2026, and the cloud service licensing terms define an account as one opened under a sales order. No sandbox or trial open without a contract was found in the pages we could read. Magento Open Source, the core with the same REST and GraphQL framework, is free under OSL 3.0, so an owner can start on a self-hosted store with no contract. Its Composer install needs keys from a Commerce Marketplace account.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the web API docs or the Swagger and GraphQL schemas (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 12198, "npmWeekly": 1317, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.adobe.com/commerce/webapi/", "openapi": "https://github.com/AdobeDocs/commerce-webapi/tree/main/src/openapi", "capabilities": [ "commerce.products", "commerce.orders", "commerce.cart", "commerce.checkout", "commerce.headless" ], "tags": [ "hosted", "self-hosted", "enterprise", "open-source", "openapi", "graphql", "oauth", "php", "sales-led", "status-page", "bug-bounty", "b2b" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 63.9, "grade": "B", "agentReady": false, "rank": 369, "ranked": true, "rankOf": 950, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 75, "payments": 30, "reliability": 55, "schema": 82, "security": 60, "transparency": 90 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Public Swagger files cover 510 REST operations for the cloud service, the GraphQL schema carries cart, checkout and order mutations, and the cloud service authenticates by OAuth 2 through Adobe IMS. No request rate limit or idempotency key was found in the API documentation, Adobe publishes no MCP server for Commerce, and a licence starts with a sales order.", "bestFor": "An agent working for a merchant already on Adobe Commerce or Magento, for catalogue, order and B2B back-office work over REST and for carts and checkout over GraphQL.", "strengths": [ "Swagger 2.0 files for the cloud service (510 operations) and for releases 2.4.6 to 2.4.9 sit in the public docs repository", "The cloud service takes OAuth 2 client credentials or user tokens from Adobe IMS, and older bearer integration tokens are off by default on 2.4 stores", "`?fields=` trims any REST response, and `searchCriteria` filters, sorts and pages every list endpoint", "Cloud service release notes list four production releases between August and 7 October 2026, each naming new endpoints", "A lifecycle policy gives end-of-support dates for every 2.4 release line, and the sub-processor list was updated on 28 September 2026" ], "weaknesses": [ "No request rate limit for the REST or GraphQL APIs was found in the reviewed documentation, and 429 handling appears only in a code sample", "No idempotency keys were found, so a retried POST can create a second order or cart item", "status.adobe.com lists three Commerce incidents marked major in September 2026, two of them longer than an hour", "The cloud service drops the customer and guest REST APIs, so shopping flows there go through GraphQL only", "No Adobe MCP server for Commerce was found, and the only official client library is a JavaScript package for App Builder" ], "agentNotes": [ "Ask which deployment the store is. The cloud service answers at `https://\u003cserver\u003e.api.commerce.adobe.com/\u003ctenant-id\u003e/` with no `/rest` prefix, and other stores at `https://\u003chost\u003e/rest/\u003cstore-view-code\u003e/`", "On the cloud service, request an IMS token with the `commerce.accs` scope and send the `Store` header to pick the store view", "On a 2.4 store, sign requests with all four integration credentials by OAuth 1.0a. A bare integration token is refused unless the merchant has switched that on", "Add `?fields=` to REST calls and set `searchCriteria[pageSize]`. Stores with input limits on cap a page at 300 items", "Don't retry `placeOrder` or a POST blindly. Read the cart or order back first, because no idempotency key was found" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.9 } ], "editorialScores": { "ergonomics": 67, "maintenance": 75, "payments": 30, "reliability": 55, "schema": 82, "security": 60, "transparency": 80 }, "provenanceScore": 99 }, "connect": { "http": "curl --location 'https://\u003cserver\u003e.api.commerce.adobe.com/\u003ctenant-id\u003e/\u003cendpoint\u003e' \\\n --header 'Authorization: Bearer \u003ctoken\u003e' \\\n --header 'Content-Type: application/json' \\\n --header 'Store: \u003call | default | \u003cstore_view_code\u003e\u003e'" }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/adobe-commerce" }, "sameCompany": [ "adobe-firefly", "adobe-pdf-extract", "adobe-photoshop-api", "adobe-acrobat-sign" ], "area": "business", "unitPrices": [ { "item": "Magento Open Source", "unit": "month", "usd": 0, "note": "OSL 3.0 core, you pay for your own hosting. Adobe Commerce prices weren't read" } ], "provenance": { "legalEntity": "Adobe Inc.", "domain": "adobe.com", "domainRegistered": "1986-11-17", "endpointOnVendorDomain": true, "terms": "https://www.adobe.com/cc-shared/assets/pdf/legal/terms/enterprise/pdfs/generalterms-na-2025v1.pdf", "privacy": "https://www.adobe.com/privacy/policy.html", "statusPage": "https://status.adobe.com", "changelog": "https://experienceleague.adobe.com/en/docs/commerce/cloud-service/release-notes", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy policy, last updated 24 October 2025, names Adobe Inc. as controller in the US, Adobe KK in Japan and Adobe Systems Software Ireland Limited elsewhere.", "The terms link is Adobe's General Terms 2025v1, effective 3 October 2025, as given on the enterprise licensing page. We read that page and the product-specific terms for Adobe Commerce as a Cloud Service (2025v1, 13 October 2025), not the General Terms PDF itself.", "Separate product-specific terms cover Adobe Commerce on Cloud (18 February 2025), on Managed Services (18 March 2025) and on-premise software (9 January 2023).", "The privacy policy says Adobe is the processor for enterprise products and that it doesn't apply to data enterprise customers collect. A data processing addendum is published at www.adobe.com/cc-shared/assets/pdf/legal/terms/enterprise/pdfs/dpa-ww.pdf.", "Cloud service endpoints are on api.commerce.adobe.com. Stores on Adobe Commerce on Cloud, on-premises and Magento Open Source answer on the merchant's own domain.", "security.txt at www.adobe.com is PGP-signed, expires 30 July 2027 and names an Intigriti programme and psirt@adobe.com.", "www.adobe.com and helpx.adobe.com answered curl with 403. The legal pages were read through WebFetch, and the helpx security bulletins weren't read at all.", "Verisign RDAP gives a registration date of 1986-11-17 for adobe.com." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/adobe-commerce.json", "live": { "slug": "adobe-commerce", "vendorStatus": { "page": "https://status.adobe.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T21:18:27.584413395Z" }, "versions": [ { "registry": "github", "name": "magento/magento2", "version": "2.4.9", "released": "2026-05-12", "seenAt": "2026-10-09T16:36:27.65482527Z" }, { "registry": "npm", "name": "@adobe/aio-commerce-sdk", "version": "2.0.0", "seenAt": "2026-10-09T16:36:26.799132643Z" } ], "githubStars": 12200, "npmWeekly": 1665, "securityTxt": { "url": "https://adobe.com/.well-known/security.txt", "state": "valid", "expires": "2027-07-30T01:00:00.000Z", "checkedAt": "2026-10-09T15:40:12.654656852Z" }, "pages": [ { "url": "https://experienceleague.adobe.com/en/docs/commerce/cloud-service/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:39:12.258194699Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d03bbfeca3c4" } ], "updatedAt": "2026-10-09T21:18:27.584413395Z" } }, "answer": "Spree Commerce scores 70.4 (BB) on agent readiness against Adobe Commerce (Magento)'s 63.9 (B), and leads in 6 of 7 scored categories. Adobe Commerce (Magento) leads on transparency \u0026 trust.", "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": "Adobe Inc.", "b": "Vendo Connect Inc", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0", "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": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-07-28", "name": "Last release" }, { "a": "", "b": "no document linked", "name": "Terms last updated" }, { "a": "2025-10-24", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "", "b": "", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "12k stars, 1.3k npm/wk", "b": "16k stars, 1.6k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Spree Commerce scores 70.4 (BB) on agent readiness against Adobe Commerce (Magento)'s 63.9 (B), and leads in 6 of 7 scored categories. Adobe Commerce (Magento) leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Adobe Commerce (Magento) or Spree Commerce?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Adobe Commerce (Magento) and Spree Commerce need an API key?" }, { "answer": "No hosted endpoint is listed for Adobe Commerce (Magento). No hosted endpoint is listed for Spree Commerce.", "question": "Can an agent call Adobe Commerce (Magento) and Spree Commerce without installing anything?" }, { "answer": "Yes. Adobe Commerce (Magento) is open source (Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0). 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 Adobe Commerce (Magento) and Spree Commerce open source?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 90 against 60" ], "also": [ "No incidents deducted, where Spree Commerce loses 5 points for them" ], "goodFor": "An agent working for a merchant already on Adobe Commerce or Magento, for catalogue, order and B2B back-office work over REST and for carts and checkout over GraphQL.", "slug": "adobe-commerce", "watchFor": "No request rate limit for the REST or GraphQL APIs was found in the reviewed documentation, and 429 handling appears only in a code sample" }, { "aheadOn": [ "Reliability, 82 against 55", "Agent ergonomics, 90 against 67", "Security \u0026 auth, 65 against 60", "Payments \u0026 pricing, 55 against 30", "Maintenance \u0026 community, 81 against 75" ], "also": [ "Agent-ready, a grade of BB or better" ], "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-bigcommerce.json", "title": "Adobe Commerce (Magento) vs BigCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-bigcommerce" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-commerce-layer.json", "title": "Adobe Commerce (Magento) vs Commerce Layer API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-commerce-layer" }, { "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-ecwid.json", "title": "Adobe Commerce (Magento) vs Ecwid by Lightspeed", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-ecwid" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-elastic-path.json", "title": "Adobe Commerce (Magento) vs Elastic Path API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-elastic-path" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.json", "title": "Adobe Commerce (Magento) vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-saleor.json", "title": "Adobe Commerce (Magento) vs Saleor API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-saleor" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-shopify.json", "title": "Adobe Commerce (Magento) vs Shopify API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-shopify" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-shopware.json", "title": "Adobe Commerce (Magento) vs Shopware", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-shopware" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-snipcart.json", "title": "Adobe Commerce (Magento) vs Snipcart API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-snipcart" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-square.json", "title": "Adobe Commerce (Magento) vs Square", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-square" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-swell.json", "title": "Adobe Commerce (Magento) vs Swell", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-vendure.json", "title": "Adobe Commerce (Magento) vs Vendure", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-wix.json", "title": "Adobe Commerce (Magento) vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-wix" }, { "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-woocommerce.json", "title": "Adobe Commerce (Magento) vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-woocommerce" }, { "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-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-spree-commerce.json", "title": "commercetools vs Spree Commerce", "url": "https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce" }, { "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": [ { "adobe-commerce": 55, "by": 27, "edge": "spree-commerce", "key": "reliability", "name": "Reliability", "spree-commerce": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "adobe-commerce": 82, "by": 3, "edge": "spree-commerce", "key": "schema", "name": "Schema \u0026 documentation", "spree-commerce": 85, "weight": 13 }, { "adobe-commerce": 67, "by": 23, "edge": "spree-commerce", "key": "ergonomics", "name": "Agent ergonomics", "spree-commerce": 90, "weight": 13 }, { "adobe-commerce": 60, "by": 5, "edge": "spree-commerce", "key": "security", "name": "Security \u0026 auth", "spree-commerce": 65, "weight": 14 }, { "adobe-commerce": 30, "by": 25, "edge": "spree-commerce", "key": "payments", "name": "Payments \u0026 pricing", "spree-commerce": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "adobe-commerce": 75, "by": 6, "edge": "spree-commerce", "key": "maintenance", "name": "Maintenance \u0026 community", "spree-commerce": 81, "weight": 7 }, { "adobe-commerce": 90, "by": 30, "edge": "adobe-commerce", "key": "transparency", "name": "Transparency \u0026 trust", "spree-commerce": 60, "weight": 7 } ], "summary": "Spree Commerce scores 70.4 (BB) on agent readiness against Adobe Commerce (Magento)'s 63.9 (B), and leads in 6 of 7 scored categories. Adobe Commerce (Magento) leads on transparency \u0026 trust. Both do commerce catalogues.", "verdicts": { "adobe-commerce": "Public Swagger files cover 510 REST operations for the cloud service, the GraphQL schema carries cart, checkout and order mutations, and the cloud service authenticates by OAuth 2 through Adobe IMS. No request rate limit or idempotency key was found in the API documentation, Adobe publishes no MCP server for Commerce, and a licence starts with a sales order.", "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/adobe-commerce-vs-spree-commerce", "json": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md", "slim": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.min.md" }, "markdown": "Spree Commerce scores 70.4 (BB) on agent readiness against Adobe Commerce (Magento)'s 63.9 (B), and leads in 6 of 7 scored categories. Adobe Commerce (Magento) leads on transparency \u0026 trust. Both do commerce catalogues.\n\n- Adobe Commerce (Magento): grade B, 63.9/100, rank #369 of 950. Markdown https://www.anchorterminal.com/tools/adobe-commerce.md · JSON https://www.anchorterminal.com/api/v1/tools/adobe-commerce.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### Adobe Commerce (Magento) (B)\n\nGood for: An agent working for a merchant already on Adobe Commerce or Magento, for catalogue, order and B2B back-office work over REST and for carts and checkout over GraphQL.\n\nAhead on:\n- Transparency \u0026 trust, 90 against 60\n\nAlso in its favour:\n- No incidents deducted, where Spree Commerce loses 5 points for them\n\nWatch for: No request rate limit for the REST or GraphQL APIs was found in the reviewed documentation, and 429 handling appears only in a code sample\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 55\n- Agent ergonomics, 90 against 67\n- Security \u0026 auth, 65 against 60\n- Payments \u0026 pricing, 55 against 30\n- Maintenance \u0026 community, 81 against 75\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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 | Adobe Commerce (Magento) | Spree Commerce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 82 | Spree Commerce +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 82 | 85 | Spree Commerce +3 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 90 | Spree Commerce +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 65 | Spree Commerce +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 55 | Spree Commerce +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 81 | Spree Commerce +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 90 | 60 | Adobe Commerce (Magento) +30 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **63.9 · B** | **70.4 · BB** | |\n\n## Facts side by side\n\n| Fact | Adobe Commerce (Magento) | Spree Commerce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Adobe Inc. | Vendo Connect Inc |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0 | 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 | no | yes |\n| Last release | 2026-10-07 | 2026-07-28 |\n| Terms last updated | | no document linked |\n| Privacy policy last updated | 2025-10-24 | no document linked |\n| Customer content may train models | | |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | 12k stars, 1.3k npm/wk | 16k stars, 1.6k npm/wk |\n\n## Verdicts\n\n**Adobe Commerce (Magento).** Public Swagger files cover 510 REST operations for the cloud service, the GraphQL schema carries cart, checkout and order mutations, and the cloud service authenticates by OAuth 2 through Adobe IMS. No request rate limit or idempotency key was found in the API documentation, Adobe publishes no MCP server for Commerce, and a licence starts with a sales order.\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### Adobe Commerce (Magento)\n\n1. Ask which deployment the store is. The cloud service answers at `https://\u003cserver\u003e.api.commerce.adobe.com/\u003ctenant-id\u003e/` with no `/rest` prefix, and other stores at `https://\u003chost\u003e/rest/\u003cstore-view-code\u003e/`\n2. On the cloud service, request an IMS token with the `commerce.accs` scope and send the `Store` header to pick the store view\n3. On a 2.4 store, sign requests with all four integration credentials by OAuth 1.0a. A bare integration token is refused unless the merchant has switched that on\n4. Add `?fields=` to REST calls and set `searchCriteria[pageSize]`. Stores with input limits on cap a page at 300 items\n5. Don't retry `placeOrder` or a POST blindly. Read the cart or order back first, because no idempotency key was found\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, Adobe Commerce (Magento) or Spree Commerce?\n\nSpree Commerce scores 70.4 (BB) on agent readiness against Adobe Commerce (Magento)'s 63.9 (B), and leads in 6 of 7 scored categories. Adobe Commerce (Magento) leads on transparency \u0026 trust.\n\n### Do Adobe Commerce (Magento) and Spree Commerce need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Adobe Commerce (Magento) and Spree Commerce without installing anything?\n\nNo hosted endpoint is listed for Adobe Commerce (Magento). No hosted endpoint is listed for Spree Commerce.\n\n### Are Adobe Commerce (Magento) and Spree Commerce open source?\n\nYes. Adobe Commerce (Magento) is open source (Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0). 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/adobe-commerce-vs-spree-commerce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"adobe-commerce\", \"b\": \"spree-commerce\"}`. From a terminal: `anchor compare adobe-commerce spree-commerce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/adobe-commerce.json and https://www.anchorterminal.com/api/v1/tools/spree-commerce.json\n\n## Other comparisons with Adobe Commerce (Magento) or Spree Commerce\n\n- [Adobe Commerce (Magento) vs BigCommerce API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-bigcommerce.md)\n- [Adobe Commerce (Magento) vs Commerce Layer API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-commerce-layer.md)\n- [Adobe Commerce (Magento) vs commercetools](https://www.anchorterminal.com/compare/adobe-commerce-vs-commercetools.md)\n- [Adobe Commerce (Magento) vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/adobe-commerce-vs-ecwid.md)\n- [Adobe Commerce (Magento) vs Elastic Path API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-elastic-path.md)\n- [Adobe Commerce (Magento) vs Medusa API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.md)\n- [Adobe Commerce (Magento) vs Saleor API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-saleor.md)\n- [Adobe Commerce (Magento) vs Shopify API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-shopify.md)\n- [Adobe Commerce (Magento) vs Shopware](https://www.anchorterminal.com/compare/adobe-commerce-vs-shopware.md)\n- [Adobe Commerce (Magento) vs Snipcart API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-snipcart.md)\n- [Adobe Commerce (Magento) vs Square](https://www.anchorterminal.com/compare/adobe-commerce-vs-square.md)\n- [Adobe Commerce (Magento) vs Swell](https://www.anchorterminal.com/compare/adobe-commerce-vs-swell.md)\n- [Adobe Commerce (Magento) vs Vendure](https://www.anchorterminal.com/compare/adobe-commerce-vs-vendure.md)\n- [Adobe Commerce (Magento) vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/adobe-commerce-vs-wix.md)\n- [Adobe Commerce (Magento) vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-woocommerce.md)\n- [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md)\n- [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md)\n- [commercetools vs Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.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": "Adobe Commerce (Magento) vs Spree Commerce", "url": "" } ], "description": "Spree Commerce scores 70.4 (BB) to Adobe Commerce's 63.9 (B) for commerce catalogues. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Adobe Commerce (Magento) B 63.9", "Spree Commerce BB 70.4", "scores" ], "h1": "Adobe Commerce (Magento) vs Spree Commerce", "image": "https://www.anchorterminal.com/assets/og/compare-adobe-commerce-vs-spree-commerce.png", "path": "/compare/adobe-commerce-vs-spree-commerce", "published": "2026-10-01", "section": "tools", "title": "Adobe Commerce vs Spree Commerce for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce" }, "tokens": { "markdown": 3000, "slim": 680 }, "version": 1 }