{ "data": { "a": { "slug": "ecwid", "name": "Ecwid by Lightspeed", "vendor": "Ecwid, Inc. (Lightspeed Commerce)", "vendorUrl": "https://www.ecwid.com", "kind": "http-api", "category": "commerce", "summary": "Ecwid by Lightspeed is a hosted online store that embeds in any website. Its REST API reads and writes products, categories, orders, customers and discounts for one store, with webhooks and a browser JavaScript API for the cart.", "url": "https://www.anchorterminal.com/tools/ecwid", "markdownUrl": "https://www.anchorterminal.com/tools/ecwid.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ecwid.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ecwid.json", "repo": "https://github.com/Ecwid/ecwid-java-api-client", "license": "Proprietary service under the Lightspeed Service Agreement. The `@lightspeed/ecom-headless` npm package is MIT and the Java API client on GitHub is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://app.ecwid.com/api/v3", "packages": [ { "registry": "npm", "name": "@lightspeed/ecom-headless" } ], "auth": "mixed", "authNotes": "Self-serve for one store. The store admin creates a custom app automatically, with a secret token and a public token sent as `Authorization: Bearer`, and no OAuth flow. Seven of the 40 access scopes are on by default, more are added in the admin, and scopes marked sensitive need a request to API support. Public apps for many stores use OAuth 2.0 and go through app review. Tokens don't expire and are revoked by uninstalling the app.", "pricing": "paid", "pricingNotes": "Starter $5 a month, Venture $35 ($29 billed yearly), Business $65 ($49) and Unlimited $149 ($119), with no transaction fee from Ecwid. The docs say only paid plans reach the API, and the pricing page does not list API access by plan. No free plan, trial or sandbox was found. Developers can email API support for a free upgrade of a test store (https://www.ecwid.com/pricing, checked 2026-10-08).", "priceSummary": "$5 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 22, "npmWeekly": 307, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.ecwid.com", "llmsTxt": "https://docs.ecwid.com/llms.txt", "capabilities": [ "commerce.products", "commerce.cart", "commerce.orders", "commerce.headless" ], "tags": [ "hosted", "closed-source", "api-key", "oauth", "llms-txt", "webhooks", "typescript", "java", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 63.2, "grade": "B", "agentReady": false, "rank": 403, "ranked": true, "rankOf": 950, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 79, "payments": 15, "reliability": 80, "schema": 66, "security": 61, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The REST API has 40 access scopes, a published limit of 600 requests a minute per token with `Retry-After` on a 429, field selection through `responseFields`, and Markdown docs with an llms.txt index. Tokens never expire, there is no test mode or idempotency key, API access needs a paid plan, and carts are built only in the browser.", "bestFor": "An agent doing back-office work on an existing Ecwid store, such as catalogue edits, order export and discount coupons.", "strengths": [ "40 access scopes split into read, update and create, plus a public token limited to enabled catalogue data and unpaid orders", "Published limit of 600 requests a minute per token, and a 429 carries a `Retry-After` header", "`responseFields` trims any response to named fields, and searches page with `offset` and `limit` up to 100", "Every docs page is served as Markdown, with `llms.txt` and `llms-full.txt` indexes", "One incident on status.ecwid.com between 10 July and 8 October 2026, a 48-minute storefront slowdown on 7 August" ], "weaknesses": [ "Access tokens never expire and change only when the app is uninstalled and installed again", "No test mode. The docs advise a separate test store, and only stores on paid plans can call the API", "No idempotency keys on REST writes found in the reviewed documentation", "OpenAPI 3.0.3 definitions are published for store profile and orders only, with no complete downloadable spec found", "The REST API has no endpoint that builds a live cart or runs checkout. Those sit in the browser JavaScript API", "The service agreement disclaims any service level commitment" ], "agentNotes": [ "Send the token as `Authorization: Bearer` to `https://app.ecwid.com/api/v3/{storeId}`. Tokens in the query string stopped working in March 2025", "Use the secret token server-side only. The public token reads enabled products and places orders that are not marked paid", "Add `responseFields`, for example `total,items(id,name,price)`, to keep responses small, and page with `offset` and `limit` (maximum 100)", "Stay under 600 requests a minute per token and wait the `Retry-After` seconds on a 429. Repeated calls with a bad token get the token and IP blocked for longer", "Work in a separate test store. There is no test mode, and `POST /orders` writes a real order with no idempotency key", "After changing an app's scopes, uninstall and reinstall it, then replace the stored tokens. The old ones stop working" ], "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.2 } ], "editorialScores": { "ergonomics": 66, "maintenance": 79, "payments": 15, "reliability": 80, "schema": 66, "security": 61, "transparency": 56 }, "provenanceScore": 87 }, "connect": { "install": "npm install @lightspeed/ecom-headless", "http": "curl \"https://app.ecwid.com/api/v3/$ECWID_STORE_ID/profile?responseFields=generalInfo(storeId,storeUrl)\" \\\n -H \"Authorization: Bearer $ECWID_SECRET_TOKEN\"" }, "letme": { "capability": "https://letme.dev/commerce.products", "tool": "https://letme.dev/ecwid" }, "area": "business", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 5, "note": "up to 10 products. The docs say only paid plans reach the API and the pricing page does not list API access by plan" }, { "item": "Venture", "unit": "month", "usd": 35, "note": "$29 a month billed yearly, up to 100 products" }, { "item": "Business", "unit": "month", "usd": 65, "note": "$49 a month billed yearly, up to 2,500 products" }, { "item": "Unlimited", "unit": "month", "usd": 149, "note": "$119 a month billed yearly, unlimited products" } ], "provenance": { "legalEntity": "Ecwid, Inc.", "domain": "ecwid.com", "domainRegistered": "2009-01-08", "endpointOnVendorDomain": true, "terms": "https://www.lightspeedhq.com/legal/lightspeed-service-agreement/", "privacy": "https://www.lightspeedhq.com/legal/privacy-policy/", "statusPage": "https://status.ecwid.com", "changelog": "https://docs.ecwid.com/changelog/ecwid-api-changelog", "securityTxt": "unknown", "checked": "2026-10-08", "notes": [ "www.ecwid.com/terms-of-service redirects to the Lightspeed Service Agreement (last updated 26 February 2026), whose contracting-entity table names Ecwid, Inc., Delaware, for Lightspeed eCom (E-Series) worldwide.", "The service agreement says API use is governed by Lightspeed's API licence agreement at https://developers.lightspeedhq.com/terms (effective 20 May 2025), which does not name Ecwid or E-Series.", "www.ecwid.com/privacy-policy and /eu-privacy-policy redirect to Lightspeed's privacy policy (effective 8 July 2026), which lists Ecwid, Inc. among the entities certified under the Data Privacy Framework.", "www.ecwid.com/.well-known/security.txt answered 403 and www.lightspeedhq.com/.well-known/security.txt answered 404, so no security.txt was read.", "RDAP for ecwid.com gives a registration date of 2009-01-08.", "The REST API answers at app.ecwid.com. Docs are hosted on GitBook at docs.ecwid.com." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ecwid.json", "live": { "slug": "ecwid", "probe": { "target": "https://app.ecwid.com/api/v3", "method": "get", "lastAt": "2026-10-10T01:37:50.465778348Z", "lastOk": true, "lastStatus": 400, "lastMs": 119, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 98, "p95ms24h": 160, "samples24h": 250, "samples30d": 317, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.ecwid.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T01:33:38.308810225Z" }, "versions": [ { "registry": "npm", "name": "@lightspeed/ecom-headless", "version": "1.2.1", "seenAt": "2026-10-09T16:51:19.442669436Z" } ], "githubStars": 22, "npmWeekly": 331, "securityTxt": { "url": "https://ecwid.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-09T15:39:56.329250846Z" }, "llmsTxt": { "url": "https://docs.ecwid.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:49.797112193Z" }, "pages": [ { "url": "https://docs.ecwid.com/changelog/ecwid-api-changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:17.899801661Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3812da5e606d" }, { "url": "https://www.ecwid.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:49:47.877133444Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "be9ee745877a" }, { "url": "https://www.lightspeedhq.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:51:39.706175578Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9364b564aad8" }, { "url": "https://www.lightspeedhq.com/legal/lightspeed-service-agreement/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:51:37.249796615Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a7dde3be944c" } ], "updatedAt": "2026-10-10T01:37:50.465778348Z" } }, "answer": "Spree Commerce scores 70.4 (BB) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 6 of 7 scored categories. Ecwid by Lightspeed 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": "Ecwid, Inc. (Lightspeed Commerce)", "b": "Vendo Connect Inc", "name": "Vendor" }, { "a": "https://app.ecwid.com/api/v3", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Lightspeed Service Agreement. The `@lightspeed/ecom-headless` npm package is MIT and the Java API client on GitHub is Apache-2.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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-07-28", "name": "Last release" }, { "a": "2026-02-26", "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": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "22 stars, 307 npm/wk", "b": "16k stars, 1.6k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Spree Commerce scores 70.4 (BB) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 6 of 7 scored categories. Ecwid by Lightspeed leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Ecwid by Lightspeed or Spree Commerce?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Ecwid by Lightspeed and Spree Commerce need an API key?" }, { "answer": "Ecwid by Lightspeed has a hosted endpoint at https://app.ecwid.com/api/v3. No hosted endpoint is listed for Spree Commerce.", "question": "Can an agent call Ecwid by Lightspeed and Spree Commerce without installing anything?" }, { "answer": "No open-source release is listed for Ecwid by Lightspeed. 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 Ecwid by Lightspeed and Spree Commerce open source?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 72 against 60" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where Spree Commerce loses 5 points for them" ], "goodFor": "An agent doing back-office work on an existing Ecwid store, such as catalogue edits, order export and discount coupons.", "slug": "ecwid", "watchFor": "Access tokens never expire and change only when the app is uninstalled and installed again" }, { "aheadOn": [ "Schema \u0026 documentation, 85 against 66", "Agent ergonomics, 90 against 66", "Payments \u0026 pricing, 55 against 15" ], "also": [ "Agent-ready, a grade of BB or better", "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-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-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-ecwid.json", "title": "BigCommerce API + MCP vs Ecwid by Lightspeed", "url": "https://www.anchorterminal.com/compare/bigcommerce-vs-ecwid" }, { "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-ecwid.json", "title": "Commerce Layer API + MCP vs Ecwid by Lightspeed", "url": "https://www.anchorterminal.com/compare/commerce-layer-vs-ecwid" }, { "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-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-elastic-path.json", "title": "Ecwid by Lightspeed vs Elastic Path API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-elastic-path" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-medusa.json", "title": "Ecwid by Lightspeed vs Medusa API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-medusa" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-saleor.json", "title": "Ecwid by Lightspeed vs Saleor API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-saleor" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-shopify.json", "title": "Ecwid by Lightspeed vs Shopify API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-shopify" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-shopware.json", "title": "Ecwid by Lightspeed vs Shopware", "url": "https://www.anchorterminal.com/compare/ecwid-vs-shopware" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-snipcart.json", "title": "Ecwid by Lightspeed vs Snipcart API + MCP", "url": "https://www.anchorterminal.com/compare/ecwid-vs-snipcart" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-square.json", "title": "Ecwid by Lightspeed vs Square", "url": "https://www.anchorterminal.com/compare/ecwid-vs-square" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-swell.json", "title": "Ecwid by Lightspeed vs Swell", "url": "https://www.anchorterminal.com/compare/ecwid-vs-swell" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-vendure.json", "title": "Ecwid by Lightspeed vs Vendure", "url": "https://www.anchorterminal.com/compare/ecwid-vs-vendure" }, { "json": "https://www.anchorterminal.com/compare/ecwid-vs-wix.json", "title": "Ecwid by Lightspeed vs Wix Stores and eCommerce API", "url": "https://www.anchorterminal.com/compare/ecwid-vs-wix" }, { "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/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": 2, "ecwid": 80, "edge": "spree-commerce", "key": "reliability", "name": "Reliability", "spree-commerce": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "ecwid": 66, "edge": "spree-commerce", "key": "schema", "name": "Schema \u0026 documentation", "spree-commerce": 85, "weight": 13 }, { "by": 24, "ecwid": 66, "edge": "spree-commerce", "key": "ergonomics", "name": "Agent ergonomics", "spree-commerce": 90, "weight": 13 }, { "by": 4, "ecwid": 61, "edge": "spree-commerce", "key": "security", "name": "Security \u0026 auth", "spree-commerce": 65, "weight": 14 }, { "by": 40, "ecwid": 15, "edge": "spree-commerce", "key": "payments", "name": "Payments \u0026 pricing", "spree-commerce": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "ecwid": 79, "edge": "spree-commerce", "key": "maintenance", "name": "Maintenance \u0026 community", "spree-commerce": 81, "weight": 7 }, { "by": 12, "ecwid": 72, "edge": "ecwid", "key": "transparency", "name": "Transparency \u0026 trust", "spree-commerce": 60, "weight": 7 } ], "summary": "Spree Commerce scores 70.4 (BB) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 6 of 7 scored categories. Ecwid by Lightspeed leads on transparency \u0026 trust. Both do commerce catalogues.", "verdicts": { "ecwid": "The REST API has 40 access scopes, a published limit of 600 requests a minute per token with `Retry-After` on a 429, field selection through `responseFields`, and Markdown docs with an llms.txt index. Tokens never expire, there is no test mode or idempotency key, API access needs a paid plan, and carts are built only in the browser.", "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/ecwid-vs-spree-commerce", "json": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.md", "slim": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.min.md" }, "markdown": "Spree Commerce scores 70.4 (BB) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 6 of 7 scored categories. Ecwid by Lightspeed leads on transparency \u0026 trust. Both do commerce catalogues.\n\n- Ecwid by Lightspeed: grade B, 63.2/100, rank #403 of 950. Markdown https://www.anchorterminal.com/tools/ecwid.md · JSON https://www.anchorterminal.com/api/v1/tools/ecwid.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### Ecwid by Lightspeed (B)\n\nGood for: An agent doing back-office work on an existing Ecwid store, such as catalogue edits, order export and discount coupons.\n\nAhead on:\n- Transparency \u0026 trust, 72 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Spree Commerce loses 5 points for them\n\nWatch for: Access tokens never expire and change only when the app is uninstalled and installed again\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 66\n- Agent ergonomics, 90 against 66\n- Payments \u0026 pricing, 55 against 15\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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 | Ecwid by Lightspeed | Spree Commerce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 82 | Spree Commerce +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 85 | Spree Commerce +19 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 90 | Spree Commerce +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 65 | Spree Commerce +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 55 | Spree Commerce +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 79 | 81 | Spree Commerce +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 60 | Ecwid by Lightspeed +12 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **63.2 · B** | **70.4 · BB** | |\n\n## Facts side by side\n\n| Fact | Ecwid by Lightspeed | Spree Commerce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Ecwid, Inc. (Lightspeed Commerce) | Vendo Connect Inc |\n| Hosted endpoint | `https://app.ecwid.com/api/v3` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the Lightspeed Service Agreement. The `@lightspeed/ecom-headless` npm package is MIT and the Java API client on GitHub is Apache-2.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 | yes | yes |\n| Last release | 2026-09-30 | 2026-07-28 |\n| Terms last updated | 2026-02-26 | 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 | not found in the text | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | yes | |\n| Popularity | 22 stars, 307 npm/wk | 16k stars, 1.6k npm/wk |\n\n## Verdicts\n\n**Ecwid by Lightspeed.** The REST API has 40 access scopes, a published limit of 600 requests a minute per token with `Retry-After` on a 429, field selection through `responseFields`, and Markdown docs with an llms.txt index. Tokens never expire, there is no test mode or idempotency key, API access needs a paid plan, and carts are built only in the browser.\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### Ecwid by Lightspeed\n\n1. Send the token as `Authorization: Bearer` to `https://app.ecwid.com/api/v3/{storeId}`. Tokens in the query string stopped working in March 2025\n2. Use the secret token server-side only. The public token reads enabled products and places orders that are not marked paid\n3. Add `responseFields`, for example `total,items(id,name,price)`, to keep responses small, and page with `offset` and `limit` (maximum 100)\n4. Stay under 600 requests a minute per token and wait the `Retry-After` seconds on a 429. Repeated calls with a bad token get the token and IP blocked for longer\n5. Work in a separate test store. There is no test mode, and `POST /orders` writes a real order with no idempotency key\n6. After changing an app's scopes, uninstall and reinstall it, then replace the stored tokens. The old ones stop working\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, Ecwid by Lightspeed or Spree Commerce?\n\nSpree Commerce scores 70.4 (BB) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 6 of 7 scored categories. Ecwid by Lightspeed leads on transparency \u0026 trust.\n\n### Do Ecwid by Lightspeed and Spree Commerce need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Ecwid by Lightspeed and Spree Commerce without installing anything?\n\nEcwid by Lightspeed has a hosted endpoint at https://app.ecwid.com/api/v3. No hosted endpoint is listed for Spree Commerce.\n\n### Are Ecwid by Lightspeed and Spree Commerce open source?\n\nNo open-source release is listed for Ecwid by Lightspeed. 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/ecwid-vs-spree-commerce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"ecwid\", \"b\": \"spree-commerce\"}`. From a terminal: `anchor compare ecwid spree-commerce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/ecwid.json and https://www.anchorterminal.com/api/v1/tools/spree-commerce.json\n\n## Other comparisons with Ecwid by Lightspeed or Spree Commerce\n\n- [Adobe Commerce (Magento) vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/adobe-commerce-vs-ecwid.md)\n- [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md)\n- [BigCommerce API + MCP vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/bigcommerce-vs-ecwid.md)\n- [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md)\n- [Commerce Layer API + MCP vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/commerce-layer-vs-ecwid.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 Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.md)\n- [Ecwid by Lightspeed vs Elastic Path API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-elastic-path.md)\n- [Ecwid by Lightspeed vs Medusa API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-medusa.md)\n- [Ecwid by Lightspeed vs Saleor API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-saleor.md)\n- [Ecwid by Lightspeed vs Shopify API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-shopify.md)\n- [Ecwid by Lightspeed vs Shopware](https://www.anchorterminal.com/compare/ecwid-vs-shopware.md)\n- [Ecwid by Lightspeed vs Snipcart API + MCP](https://www.anchorterminal.com/compare/ecwid-vs-snipcart.md)\n- [Ecwid by Lightspeed vs Square](https://www.anchorterminal.com/compare/ecwid-vs-square.md)\n- [Ecwid by Lightspeed vs Swell](https://www.anchorterminal.com/compare/ecwid-vs-swell.md)\n- [Ecwid by Lightspeed vs Vendure](https://www.anchorterminal.com/compare/ecwid-vs-vendure.md)\n- [Ecwid by Lightspeed vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/ecwid-vs-wix.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- [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": "Ecwid by Lightspeed vs Spree Commerce", "url": "" } ], "description": "Spree Commerce scores 70.4 (BB) to Ecwid by Lightspeed's 63.2 (B) for commerce catalogues. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Ecwid by Lightspeed B 63.2", "Spree Commerce BB 70.4", "scores" ], "h1": "Ecwid by Lightspeed vs Spree Commerce", "image": "https://www.anchorterminal.com/assets/og/compare-ecwid-vs-spree-commerce.png", "path": "/compare/ecwid-vs-spree-commerce", "published": "2026-10-01", "section": "tools", "title": "Ecwid by Lightspeed vs Spree Commerce for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce" }, "tokens": { "markdown": 2950, "slim": 780 }, "version": 1 }