{ "data": { "a": { "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" } }, "answer": "WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Spree Commerce's 70.4 (BB), and leads in 3 of 7 scored categories. Spree Commerce leads on schema \u0026 documentation, agent ergonomics and security \u0026 auth.", "b": { "slug": "woocommerce", "name": "WooCommerce API + MCP", "vendor": "WooCommerce (Automattic)", "vendorUrl": "https://woocommerce.com", "kind": "http-api", "category": "commerce", "summary": "Open-source commerce plugin for WordPress that you host yourself.", "url": "https://www.anchorterminal.com/tools/woocommerce", "markdownUrl": "https://www.anchorterminal.com/tools/woocommerce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/woocommerce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/woocommerce.json", "repo": "https://github.com/woocommerce/woocommerce", "license": "GPL-3.0", "transports": [ "http", "streamable-http", "stdio" ], "packages": [ { "registry": "npm", "name": "@woocommerce/woocommerce-rest-api" }, { "registry": "pypi", "name": "woocommerce" }, { "registry": "npm", "name": "@automattic/mcp-wordpress-remote" } ], "auth": "mixed", "authNotes": "REST API keys (consumer key and secret) with read, write or read_write permission, sent as HTTP Basic over HTTPS. The Store API needs no key for browsing and uses a nonce or Cart-Token for cart and checkout calls. The MCP adapter takes a WordPress Application Password and acts with that user's capabilities. The deprecated /wp-json/woocommerce/mcp endpoint used REST keys.", "pricing": "free", "pricingNotes": "The plugin is free under GPL with no platform fee or revenue share. You pay for hosting, which Woo puts at $25 to $350 a month for most stores, extensions at $29 to $299 a year each, and card processing, about 2.9% + 30 cents per US transaction with WooPayments (https://woocommerce.com/pricing/).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402 in core. Payments go through whichever gateway the store installs.", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": 10535, "npmWeekly": 63554, "pypiWeekly": 24657, "asOf": "2026-09-30" }, "docsUrl": "https://developer.woocommerce.com/docs/", "llmsTxt": "https://developer.woocommerce.com/llms.txt", "capabilities": [ "commerce.products", "commerce.cart", "commerce.checkout", "commerce.orders", "commerce.headless" ], "tags": [ "open-source", "self-hosted", "local", "mcp", "llms-txt", "webhooks", "python", "typescript" ], "lastRelease": "2026-09-22", "graded": true, "anchor": { "graded": true, "score": 72.9, "grade": "BB", "agentReady": true, "rank": 97, "ranked": true, "rankOf": 950, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 77, "security": 55, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page.", "bestFor": "Merchants already on WordPress and agents that need a cart and checkout without a vendor account.", "strengths": [ "Free GPL software with no platform fee or revenue share", "Store API runs carts, coupons and checkout with a Cart-Token instead of a key", "Code examples in five languages on every REST endpoint, and official JavaScript and Python clients", "Automattic's HackerOne bug bounty covers WooCommerce core", "Six stable releases between 7 July and 22 September 2026, CI green on trunk" ], "weaknesses": [ "Uptime, speed and security depend on each store's host and plugins. No vendor status page", "MCP is a developer preview behind the mcp_integration flag, with 7 abilities", "REST docs allow the consumer key and secret in the query string", "Store API rate limiting is off by default", "No OpenAPI file, so the contract only comes from a live store" ], "agentNotes": [ "Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL", "Get a Cart-Token with GET /wp-json/wc/store/v1/cart and send it on every cart and checkout call instead of a nonce", "Add `_fields=id,name,price` to REST calls to cut response size", "Page with per_page up to 100 and stop at X-WP-TotalPages", "Product delete only trashes unless you pass force true, so check the trash before assuming it's gone" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.9 } ], "editorialScores": { "ergonomics": 83, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 77, "security": 55, "transparency": 86 }, "provenanceScore": 63 }, "connect": { "http": "curl \"https://yourstore.com/wp-json/wc/v3/products?per_page=5\" \\\n -u \"$WC_CONSUMER_KEY:$WC_CONSUMER_SECRET\"", "claudeCode": "claude mcp add --env WP_API_URL=https://yourstore.com/wp-json/mcp/mcp-adapter-default-server --env WP_API_USERNAME=$WP_USER --env WP_API_PASSWORD=$WP_APP_PASSWORD woocommerce_store -- npx -y @automattic/mcp-wordpress-remote@latest", "config": { "mcpServers": { "woocommerce_store": { "args": [ "-y", "@automattic/mcp-wordpress-remote@latest" ], "command": "npx", "env": { "WP_API_PASSWORD": "${WP_APP_PASSWORD}", "WP_API_URL": "https://yourstore.com/wp-json/mcp/mcp-adapter-default-server", "WP_API_USERNAME": "${WP_USER}" } } } } }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/woocommerce" }, "area": "business", "unitPrices": [ { "item": "WooCommerce plugin", "unit": "month", "usd": 0, "note": "GPL, you pay for your own hosting" }, { "item": "WooPayments US card rate", "unit": "pct", "usd": 2.9, "note": "plus 30 cents per transaction, optional gateway" } ], "provenance": { "legalEntity": "WooCommerce, Inc.", "domain": "woocommerce.com", "domainRegistered": "2010-01-09", "endpointOnVendorDomain": false, "terms": "https://wordpress.com/tos/", "privacy": "https://automattic.com/privacy/", "statusPage": "", "changelog": "https://developer.woocommerce.com/changelog/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "woocommerce.com/terms-conditions redirects to the WordPress.com terms, which name WooCommerce, Inc. as an Automattic company", "The API runs on each merchant's own domain" ], "score": 63 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/woocommerce.json", "live": { "slug": "woocommerce", "versions": [ { "registry": "github", "name": "woocommerce/woocommerce", "version": "11.2.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:28:34.182850133Z" }, { "registry": "npm", "name": "@automattic/mcp-wordpress-remote", "version": "0.5.1", "seenAt": "2026-10-09T17:28:33.056672179Z" }, { "registry": "npm", "name": "@woocommerce/woocommerce-rest-api", "version": "1.0.2", "seenAt": "2026-10-09T17:28:31.937272951Z" }, { "registry": "pypi", "name": "woocommerce", "version": "3.0.0", "released": "2021-03-13", "seenAt": "2026-10-09T17:28:32.859775695Z" } ], "githubStars": 10542, "npmWeekly": 49055, "pypiWeekly": 29084, "securityTxt": { "url": "https://woocommerce.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:22.112615062Z" }, "llmsTxt": { "url": "https://developer.woocommerce.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:03:01.376834452Z" }, "domain": { "domain": "woocommerce.com", "registered": "2010-01-09", "source": "https://rdap.verisign.com/com/v1/domain/woocommerce.com", "checkedAt": "2026-10-04T13:03:39.15219252Z" }, "pages": [ { "url": "https://developer.woocommerce.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:35:27.079036122Z", "changedAt": "2026-10-08T18:17:22.796442961Z", "fingerprint": "24c7d32554f1" }, { "url": "https://woocommerce.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:47:30.455333244Z", "changedAt": "2026-10-09T18:47:30.455333244Z", "fingerprint": "f20472793613" }, { "url": "https://automattic.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:32:49.633621248Z", "changedAt": "2026-10-09T18:32:49.633621248Z", "fingerprint": "233f936cea6a" }, { "url": "https://wordpress.com/tos/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:47:32.490186083Z", "changedAt": "2026-10-07T18:10:29.658725622Z", "fingerprint": "7a21fafe2264" } ], "updatedAt": "2026-10-09T18:47:32.490186083Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Vendo Connect Inc", "b": "WooCommerce (Automattic)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence", "b": "GPL-3.0", "name": "Licence" }, { "a": "none", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-07-28", "b": "2026-09-22", "name": "Last release" }, { "a": "no document linked", "b": "2026-10-06", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "16k stars, 1.6k npm/wk", "b": "11k stars, 64k npm/wk, 25k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Spree Commerce's 70.4 (BB), and leads in 3 of 7 scored categories. Spree Commerce leads on schema \u0026 documentation, agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Spree Commerce or WooCommerce API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Spree Commerce and WooCommerce API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for Spree Commerce. WooCommerce API + MCP runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Spree Commerce and WooCommerce API + MCP without installing anything?" }, { "answer": "Yes. 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). WooCommerce API + MCP is open source (GPL-3.0).", "question": "Are Spree Commerce and WooCommerce API + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 85 against 77", "Agent ergonomics, 90 against 83", "Security \u0026 auth, 65 against 55" ], "also": null, "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" }, { "aheadOn": [ "Payments \u0026 pricing, 60 against 55", "Transparency \u0026 trust, 75 against 60" ], "also": [ "Runs on your own machine", "No incidents deducted, where Spree Commerce loses 5 points for them" ], "goodFor": "Merchants already on WordPress and agents that need a cart and checkout without a vendor account.", "slug": "woocommerce", "watchFor": "Uptime, speed and security depend on each store's host and plugins. No vendor status page" } ], "job": { "capability": "commerce.products", "name": "Commerce catalogues" }, "others": [ { "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/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/bigcommerce-vs-woocommerce.json", "title": "BigCommerce API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-woocommerce" }, { "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/commerce-layer-vs-woocommerce.json", "title": "Commerce Layer API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-woocommerce" }, { "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/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/ecwid-vs-woocommerce.json", "title": "Ecwid by Lightspeed vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-woocommerce" }, { "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/elastic-path-vs-woocommerce.json", "title": "Elastic Path API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/elastic-path-vs-woocommerce" }, { "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/medusa-vs-woocommerce.json", "title": "Medusa API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/medusa-vs-woocommerce" }, { "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/saleor-vs-woocommerce.json", "title": "Saleor API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/saleor-vs-woocommerce" }, { "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/shopify-vs-woocommerce.json", "title": "Shopify API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/shopify-vs-woocommerce" }, { "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/shopware-vs-woocommerce.json", "title": "Shopware vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/shopware-vs-woocommerce" }, { "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/snipcart-vs-woocommerce.json", "title": "Snipcart API + MCP vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/snipcart-vs-woocommerce" }, { "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/square-vs-woocommerce.json", "title": "Square vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/square-vs-woocommerce" }, { "json": "https://www.anchorterminal.com/compare/swell-vs-woocommerce.json", "title": "Swell vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/swell-vs-woocommerce" }, { "json": "https://www.anchorterminal.com/compare/vendure-vs-woocommerce.json", "title": "Vendure vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/vendure-vs-woocommerce" }, { "json": "https://www.anchorterminal.com/compare/wix-vs-woocommerce.json", "title": "Wix Stores and eCommerce API vs WooCommerce API + MCP", "url": "https://www.anchorterminal.com/compare/wix-vs-woocommerce" } ], "scores": [ { "by": 2, "edge": "spree-commerce", "key": "reliability", "name": "Reliability", "spree-commerce": 82, "weight": 16, "woocommerce": 80 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "spree-commerce", "key": "schema", "name": "Schema \u0026 documentation", "spree-commerce": 85, "weight": 13, "woocommerce": 77 }, { "by": 7, "edge": "spree-commerce", "key": "ergonomics", "name": "Agent ergonomics", "spree-commerce": 90, "weight": 13, "woocommerce": 83 }, { "by": 10, "edge": "spree-commerce", "key": "security", "name": "Security \u0026 auth", "spree-commerce": 65, "weight": 14, "woocommerce": 55 }, { "by": 5, "edge": "woocommerce", "key": "payments", "name": "Payments \u0026 pricing", "spree-commerce": 55, "weight": 10, "woocommerce": 60 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "woocommerce", "key": "maintenance", "name": "Maintenance \u0026 community", "spree-commerce": 81, "weight": 7, "woocommerce": 82 }, { "by": 15, "edge": "woocommerce", "key": "transparency", "name": "Transparency \u0026 trust", "spree-commerce": 60, "weight": 7, "woocommerce": 75 } ], "summary": "WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Spree Commerce's 70.4 (BB), and leads in 3 of 7 scored categories. Spree Commerce leads on schema \u0026 documentation, agent ergonomics and security \u0026 auth. Both do commerce catalogues.", "verdicts": { "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.", "woocommerce": "Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce", "json": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.md", "slim": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.min.md" }, "markdown": "WooCommerce API + MCP scores 72.9 (BB) on agent readiness against Spree Commerce's 70.4 (BB), and leads in 3 of 7 scored categories. Spree Commerce leads on schema \u0026 documentation, agent ergonomics and security \u0026 auth. Both do commerce catalogues.\n\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- WooCommerce API + MCP: grade BB, 72.9/100, rank #97 of 950. Markdown https://www.anchorterminal.com/tools/woocommerce.md · JSON https://www.anchorterminal.com/api/v1/tools/woocommerce.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### 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- Schema \u0026 documentation, 85 against 77\n- Agent ergonomics, 90 against 83\n- Security \u0026 auth, 65 against 55\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### WooCommerce API + MCP (BB)\n\nGood for: Merchants already on WordPress and agents that need a cart and checkout without a vendor account.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 55\n- Transparency \u0026 trust, 75 against 60\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Spree Commerce loses 5 points for them\n\nWatch for: Uptime, speed and security depend on each store's host and plugins. No vendor status page\n\n\n## Score by category\n\n| Category | Weight | Spree Commerce | WooCommerce API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 82 | 80 | Spree Commerce +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 77 | Spree Commerce +8 |\n| Agent ergonomics | 13% (16.2 this run) | 90 | 83 | Spree Commerce +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 55 | Spree Commerce +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 60 | WooCommerce API + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 82 | WooCommerce API + MCP +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 75 | WooCommerce API + MCP +15 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **70.4 · BB** | **72.9 · BB** | |\n\n## Facts side by side\n\n| Fact | Spree Commerce | WooCommerce API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Vendo Connect Inc | WooCommerce (Automattic) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence | GPL-3.0 |\n| Tools exposed | none | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-07-28 | 2026-09-22 |\n| Terms last updated | no document linked | 2026-10-06 |\n| Privacy policy last updated | no document linked | no date given |\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 | | not found in the text |\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 | 16k stars, 1.6k npm/wk | 11k stars, 64k npm/wk, 25k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\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**WooCommerce API + MCP.** Free GPL software with no platform fee or revenue share. Uptime, speed and security depend on each store's host and plugins. No vendor status page.\n\n## Before you call either\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### WooCommerce API + MCP\n\n1. Create a REST key with read permission only for reporting tasks, and send it in the Authorization header, never the URL\n2. Get a Cart-Token with GET /wp-json/wc/store/v1/cart and send it on every cart and checkout call instead of a nonce\n3. Add `_fields=id,name,price` to REST calls to cut response size\n4. Page with per_page up to 100 and stop at X-WP-TotalPages\n5. Product delete only trashes unless you pass force true, so check the trash before assuming it's gone\n\n## Questions\n\n### Which is better for AI agents, Spree Commerce or WooCommerce API + MCP?\n\nWooCommerce API + MCP scores 72.9 (BB) on agent readiness against Spree Commerce's 70.4 (BB), and leads in 3 of 7 scored categories. Spree Commerce leads on schema \u0026 documentation, agent ergonomics and security \u0026 auth.\n\n### Do Spree Commerce and WooCommerce API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Spree Commerce and WooCommerce API + MCP without installing anything?\n\nNo hosted endpoint is listed for Spree Commerce. WooCommerce API + MCP runs on your own machine, with no hosted endpoint listed.\n\n### Are Spree Commerce and WooCommerce API + MCP open source?\n\nYes. 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). WooCommerce API + MCP is open source (GPL-3.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"spree-commerce\", \"b\": \"woocommerce\"}`. From a terminal: `anchor compare spree-commerce woocommerce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/spree-commerce.json and https://www.anchorterminal.com/api/v1/tools/woocommerce.json\n\n## Other comparisons with Spree Commerce or WooCommerce API + MCP\n\n- [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.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- [BigCommerce API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/bigcommerce-vs-woocommerce.md)\n- [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md)\n- [Commerce Layer API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/commerce-layer-vs-woocommerce.md)\n- [commercetools vs Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.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- [Ecwid by Lightspeed vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-woocommerce.md)\n- [Elastic Path API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.md)\n- [Elastic Path API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/elastic-path-vs-woocommerce.md)\n- [Medusa API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md)\n- [Medusa API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/medusa-vs-woocommerce.md)\n- [Saleor API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.md)\n- [Saleor API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/saleor-vs-woocommerce.md)\n- [Shopify API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.md)\n- [Shopify API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/shopify-vs-woocommerce.md)\n- [Shopware vs Spree Commerce](https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.md)\n- [Shopware vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/shopware-vs-woocommerce.md)\n- [Snipcart API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.md)\n- [Snipcart API + MCP vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/snipcart-vs-woocommerce.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- [Square vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/square-vs-woocommerce.md)\n- [Swell vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/swell-vs-woocommerce.md)\n- [Vendure vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/vendure-vs-woocommerce.md)\n- [Wix Stores and eCommerce API vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/wix-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": "Spree Commerce vs WooCommerce API + MCP", "url": "" } ], "description": "WooCommerce scores 72.9 (BB) to Spree Commerce's 70.4 (BB) for commerce catalogues. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Spree Commerce BB 70.4", "WooCommerce API + MCP BB 72.9", "scores" ], "h1": "Spree Commerce vs WooCommerce API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-spree-commerce-vs-woocommerce.png", "path": "/compare/spree-commerce-vs-woocommerce", "published": "2026-10-01", "section": "tools", "title": "Spree Commerce vs WooCommerce for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce" }, "tokens": { "markdown": 2850, "slim": 730 }, "version": 1 }