Head to head · Commerce products · October 2026 research run
Ecwid by Lightspeed vs Square
Square scores 69.2 (B) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 5 of 7 scored categories. Ecwid by Lightspeed leads on reliability. Both do commerce products.
Which one, for what
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 58
Watch for
Access tokens never expire and change only when the app is uninstalled and installed again
Square B
Good for Agents working for a seller already on Square, on catalogue, inventory, orders, payment links and customers, online and in person.
Ahead on
- Schema & documentation, 87 against 66
- Agent ergonomics, 83 against 66
- Security & auth, 67 against 61
- Payments & pricing, 40 against 15
Also in its favour
- Runs on your own machine
Watch for
The MCP server is marked beta, and the remote server reaches production data only
Score by category
| Category | Weight this run | Ecwid by Lightspeed | Square | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 58 | Ecwid by Lightspeed +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 66 | 87 | Square +21 |
| Agent ergonomics | 13%16.2 | 66 | 83 | Square +17 |
| Security & auth | 14%17.5 | 61 | 67 | Square +6 |
| Payments & pricing | 10%12.5 | 15 | 40 | Square +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 79 | 81 | Square +2 |
| Transparency & trust | 7%8.8 | 72 | 70 | Ecwid by Lightspeed +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 63.2 · B | 69.2 · B |
Facts side by side
| Fact | Ecwid by Lightspeed | Square |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Ecwid, Inc. (Lightspeed Commerce) | Block, Inc. |
| Hosted endpoint | https://app.ecwid.com/api/v3 | https://mcp.squareup.com/mcp |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| 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 | Proprietary service under the Square Developer Terms of Service. The MCP server and the OpenAPI specification on GitHub are Apache 2.0, and the Node.js SDK is MIT |
| Tools exposed | none | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-09-16 |
| Terms last updated | 2026-02-26 | 2026-09-10 |
| Privacy policy last updated | no date given | 2026-09-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 22 stars, 307 npm/wk | 454k npm/wk, 72k PyPI/wk |
Verdicts
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.
Square
The REST API has a public OpenAPI 3.0 spec, OAuth scopes split by read and write for each resource, idempotency keys on writes and a free sandbox. The MCP server is in beta and its remote instance reaches production only. No numeric REST rate limits or SLA were found, and the status page recorded widespread errors on 27 September 2026.
Before you call either
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
Square
- Test against the sandbox first with the local MCP server and
SANDBOX=true. The remote server at mcp.squareup.com reaches production only - Set
DISALLOW_WRITES=trueon the local MCP server when the task only reads - Call
get_service_info, thenget_type_info, before eachmake_api_request. The request body is otherwise untyped - Send a fresh
idempotency_keyon every write, and reuse it when retrying the same write - Pin
Square-Versionin each request. Use a page cursor within 5 minutes of receiving it
Questions
Which is better for AI agents, Ecwid by Lightspeed or Square?
Square scores 69.2 (B) on agent readiness against Ecwid by Lightspeed's 63.2 (B), and leads in 5 of 7 scored categories. Ecwid by Lightspeed leads on reliability.
Do Ecwid by Lightspeed and Square need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Ecwid by Lightspeed and Square without installing anything?
Yes. Ecwid by Lightspeed has a hosted endpoint at https://app.ecwid.com/api/v3 and Square at https://mcp.squareup.com/mcp.
Other comparisons with Ecwid by Lightspeed or Square
- Adobe Commerce (Magento) vs Ecwid by Lightspeed
- Adobe Commerce (Magento) vs Square
- BigCommerce API + MCP vs Ecwid by Lightspeed
- BigCommerce API + MCP vs Square
- Commerce Layer API + MCP vs Ecwid by Lightspeed
- Commerce Layer API + MCP vs Square
- commercetools vs Ecwid by Lightspeed
- commercetools vs Square
- 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 Swell
- Ecwid by Lightspeed vs Vendure
- Ecwid by Lightspeed vs Wix Stores and eCommerce API
- Ecwid by Lightspeed vs WooCommerce API + MCP
- Elastic Path API + MCP vs Square
- Medusa API + MCP vs Square
- Saleor API + MCP vs Square
- Shopify API + MCP vs Square
- Shopware vs Square
- Snipcart API + MCP vs Square
- Square vs Swell
- Square vs Vendure
- Square vs Wix Stores and eCommerce API
- Square vs WooCommerce API + MCP
Machine-readable
- This page as Markdown
/compare/ecwid-vs-square.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ecwid.json·/api/v1/tools/square.json - From a terminal
anchor compare ecwid square(the CLI) - Over MCP
compare_tools {"a": "ecwid", "b": "square"}at/mcp, no key