Head to head · Commerce products · October 2026 research run
commercetools vs Ecwid by Lightspeed
commercetools scores 71.3 (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 reliability. Both do commerce products.
Which one, for what
Good for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.
Ahead on
- Schema & documentation, 86 against 66
- Agent ergonomics, 83 against 66
- Security & auth, 70 against 61
- Payments & pricing, 20 against 15
- Maintenance & community, 85 against 79
- Transparency & trust, 81 against 72
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
No public price. The pricing page describes order-based pricing and sends buyers to sales
Good for An agent doing back-office work on an existing Ecwid store, such as catalogue edits, order export and discount coupons.
Ahead on
- Reliability, 80 against 73
Watch for
Access tokens never expire and change only when the app is uninstalled and installed again
Score by category
| Category | Weight this run | commercetools | Ecwid by Lightspeed | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 73 | 80 | Ecwid by Lightspeed +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 66 | commercetools +20 |
| Agent ergonomics | 13%16.2 | 83 | 66 | commercetools +17 |
| Security & auth | 14%17.5 | 70 | 61 | commercetools +9 |
| Payments & pricing | 10%12.5 | 20 | 15 | commercetools +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 85 | 79 | commercetools +6 |
| Transparency & trust | 7%8.8 | 81 | 72 | commercetools +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 71.3 · BB | 63.2 · B |
Facts side by side
| Fact | commercetools | Ecwid by Lightspeed |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | commercetools GmbH | Ecwid, Inc. (Lightspeed Commerce) |
| Hosted endpoint | https://api.{region}.commercetools.com/{projectKey} | https://app.ecwid.com/api/v3 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MIT | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-09-30 |
| Terms last updated | no date given | 2026-02-26 |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 221k npm/wk | 22 stars, 307 npm/wk |
Verdicts
commercetools
A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and the HTTP API publishes no platform-wide rate limit. A 60-day trial needs no card.
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.
Before you call either
commercetools
- Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
- Send the resource's current
versionwith every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed - Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body
- For MCP, ask for an API Client scoped to
mcp:{projectKey}:{mcpServerKey}and a server limited to the tools the task needs, notall - Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request
Ecwid by Lightspeed
- Send the token as
Authorization: Bearertohttps://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 exampletotal,items(id,name,price), to keep responses small, and page withoffsetandlimit(maximum 100) - Stay under 600 requests a minute per token and wait the
Retry-Afterseconds 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 /orderswrites 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
Questions
Which is better for AI agents, commercetools or Ecwid by Lightspeed?
commercetools scores 71.3 (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 reliability.
Do commercetools and Ecwid by Lightspeed need an API key?
commercetools uses an OAuth sign-in. Ecwid by Lightspeed takes an API key or an OAuth sign-in.
Can an agent call commercetools and Ecwid by Lightspeed without installing anything?
Yes. commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey} and Ecwid by Lightspeed at https://app.ecwid.com/api/v3.
Other comparisons with commercetools or Ecwid by Lightspeed
- Adobe Commerce (Magento) vs commercetools
- Adobe Commerce (Magento) vs Ecwid by Lightspeed
- BigCommerce API + MCP vs commercetools
- BigCommerce API + MCP vs Ecwid by Lightspeed
- Commerce Layer API + MCP vs commercetools
- Commerce Layer API + MCP vs Ecwid by Lightspeed
- commercetools vs Elastic Path API + MCP
- commercetools vs Medusa API + MCP
- commercetools vs Saleor API + MCP
- commercetools vs Shopify API + MCP
- commercetools vs Shopware
- commercetools vs Snipcart API + MCP
- commercetools vs Square
- commercetools vs Swell
- commercetools vs Vendure
- commercetools vs Wix Stores and eCommerce API
- commercetools vs WooCommerce API + MCP
- Ecwid by Lightspeed vs Elastic Path API + MCP
- Ecwid by Lightspeed vs Medusa API + MCP
- Ecwid by Lightspeed vs Saleor API + MCP
- Ecwid by Lightspeed vs Shopify API + MCP
- Ecwid by Lightspeed vs Shopware
- Ecwid by Lightspeed vs Snipcart API + MCP
- Ecwid by Lightspeed vs Square
- Ecwid by Lightspeed vs Swell
- Ecwid by Lightspeed vs Vendure
- Ecwid by Lightspeed vs Wix Stores and eCommerce API
- Ecwid by Lightspeed vs WooCommerce API + MCP
Machine-readable
- This page as Markdown
/compare/commercetools-vs-ecwid.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/commercetools.json·/api/v1/tools/ecwid.json - From a terminal
anchor compare commercetools ecwid(the CLI) - Over MCP
compare_tools {"a": "commercetools", "b": "ecwid"}at/mcp, no key