Head to head · Commerce catalogues · October 2026 research run

Adobe Commerce (Magento) vs Ecwid by Lightspeed

Ecwid by Lightspeed scores 60.2 (C) on agent readiness against Adobe Commerce (Magento)'s 50.5 (D), and leads in 3 of 7 scored categories. Adobe Commerce (Magento) leads on schema & documentation, payments & pricing and transparency & trust. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

Adobe Commerce (Magento) D

Best for An agent working for a merchant already on Adobe Commerce or Magento, for catalogue, order and B2B back-office work over REST and for carts and checkout over GraphQL.

Ahead on

  • Schema & documentation, 82 against 66
  • Payments & pricing, 45 against 23
  • Transparency & trust, 87 against 72

Also in its favour

  • Open source

Watch for

No request rate limit for the REST or GraphQL APIs was found in the reviewed documentation, and 429 handling is documented only for payment rate limiting

Ecwid by Lightspeed C

Best for An agent doing back-office work on an existing Ecwid store, such as catalogue edits, order export and discount coupons.

Ahead on

  • Reliability, 60 against 55

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Adobe Commerce (Magento) loses 15 points for them

Watch for

Access tokens never expire and change only when the app is uninstalled and installed again

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Adobe Commerce (Magento) +22

Adobe Commerce (Magento) 45

No x402, MPP or L402 in the API docs or the schemas (0). business.adobe.com timed out on 8 October and again on 2 November 2026 (its robots.txt didn't answer), so the pricing page is unread and scored as absent. The cloud service licensing terms define an account as one opened under a sales order (0). Magento Open Source, the core with the same REST and GraphQL framework, is free under OSL 3.0 with no card (20). Its Composer install needs authentication keys from a Commerce Marketplace account, which a person creates. The public Git repository can be cloned with no account and the install guide points contributors to it, so half the points (10). 0 + 0 + 20 + 10 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Ecwid by Lightspeed 23

No x402, MPP or L402 (0). Plan prices are public, Starter $5, Venture $35, Business $65 and Unlimited $149 a month, with nothing per call (10). No free plan or trial was found on the pricing page, and the docs say only paid plans reach the API. Developers can email API support for a free upgrade of a test store, which earns part of the line (5). A person signs up in a browser and copies the token from the admin (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Schema & documentation Adobe Commerce (Magento) +16

Adobe Commerce (Magento) 82

Swagger 2.0 YAML files in the public docs repository for the cloud service (525 operations, version November 2026, updated 29 October) and for the admin, customer and guest APIs of 2.4.6 to 2.4.9, plus GraphQL introspection JSON for each (25). Every page on developer.adobe.com is also served as Markdown at the same path with .md. No llms.txt there, and Experience League has one for the operations and admin guides (10). All 525 cloud service operations carry a description, with a median length of 40 characters and 141 under 30, and 239 of 246 GraphQL queries and mutations have one, per the 8 October check. None says when not to use a call (11). Definitions are typed and GraphQL uses enums, while searchCriteria parameters are plain strings and custom_attributes and extension_attributes are open (10). Tutorials with full requests and responses, a status code table, and 400 (220 operations), 401 (525) and 500 (159) responses in the spec, with no list of error codes (11). A schema per release, cloud service release notes for each release and release notes for each 2.4 version (15). 25 + 10 + 11 + 10 + 11 + 15 = 82.

Ecwid by Lightspeed 66

OpenAPI 3.0.3 definitions are embedded in the reference for store profile, store logo, orders and order extra fields only, marked version 0.0.1. No complete downloadable spec was found (10). llms.txt, llms-full.txt and a Markdown twin of every page (10). Reference pages state what each call does and which scopes it needs, with little on when not to use one (12). Parameters are typed in tables, and the published OpenAPI fragments carry almost no enums or required markers (9). Request and response examples on reference pages and a page of named error codes by area (12). The version sits in the path as /api/v3 and a dated changelog marks breaking changes, though it was silent from 30 April to 30 September 2026 (13).

Transparency & trust Adobe Commerce (Magento) +15

Adobe Commerce (Magento) 87

Magento Open Source is OSL 3.0. Adobe Commerce is proprietary under Adobe's General Terms (2025v1, 3 October 2025) and a product-specific document for each deployment, all public (22). The privacy policy of 24 October 2025 says Adobe is the processor for enterprise products and that the policy doesn't cover data its customers collect. The cloud service terms keep customer data for the licence term and allow 30 days to export after it ends. A data processing addendum is published, which we didn't read (22). The lifecycle policy gives three years of standard support and end dates for every release from 2.4.4 to 2.4.9, and says Cloud environments on unsupported versions lose traffic from 1 June 2027. No notice period for API changes on the cloud service was found (18). The sub-processor list, updated 28 September 2026, names seven for Adobe Commerce with countries or regions, among them Microsoft, Platform.sh, Fastly and New Relic (18). 22 + 22 + 18 + 18 = 80. The privacy, terms and sub-processor pages on www.adobe.com are per the 8 October check (not re-read on 2 November).

Ecwid by Lightspeed 72

Closed service with a published service agreement, updated 26 February 2026, that names Ecwid, Inc. as the contracting entity for E-Series (15). Privacy policy effective 8 July 2026 and a public DPA, both written for the whole Lightspeed group. Retention is stated as for as long as reasonably needed, with no periods (18). No deprecation policy was found. The changelog marks breaking changes, and the March 2025 entry on query-string tokens announces a change already made (5). The sub-processor list, updated 30 September 2026, gives purpose, product line and country for each provider, with E-Series rows (18).

Reliability Ecwid by Lightspeed +5

Adobe Commerce (Magento) 55

Graded with the hosted lines, because Adobe runs the cloud service and Adobe Commerce on Cloud. status.adobe.com lists Adobe Commerce with its components and regions, per the 8 October check (20). The page is drawn by script from Adobe's status data endpoint on data.status.adobe.com, a site's internal data endpoint that we don't call, and links no feed. The 8 October reading taken from that endpoint (eight Commerce events in September, three marked major) is struck, and the 90 days from 4 August couldn't be read on 2 November, so the window isn't credited (5 of 30, no readable history). Input limits are published with numbers (20 items in a list input, 5,000 for asynchronous calls, 300 a page, GraphQL complexity 300 and depth 20), and payment rate limiting from 2.4.7 is configurable per guest and customer, but no request rate limit for the APIs was found (5). The payment rate-limiting page documents a 429 on REST, and the server-to-server sample retries on 429 after retry-after, with no written backoff guidance and no idempotency keys found (5). The Unified SLA's Actionability Addendum of 23 July 2026 covers Adobe Commerce, per the 8 October check. We didn't read the percentage (10). Generally available (10). 20 + 5 + 5 + 5 + 10 + 10 = 55.

Ecwid by Lightspeed 60

Graded as a hosted service, on the REST API. Atlassian Statuspage at status.ecwid.com with six components, API among them (20). The incident history for most of the 90 days from 4 August couldn't be read on 2 November. /history draws its list by script, /history.atom and /history.rss redirect to an inactive feed, and robots.txt disallows /api/ and /embed/. The front page shows no incidents from 19 October to 2 November. The 8 October reading of one 48-minute storefront slowdown on 7 August came from the disallowed /api/ path and is struck, so the window is scored as unread (5, was 25, which wasn't a checklist value). 600 requests a minute per token is published (15). A 429 carries Retry-After, but no backoff guidance and no idempotency keys for REST writes were found (10). The Lightspeed Service Agreement disclaims any service level commitment (0). The REST API is generally available at /api/v3 (10). 20 + 5 + 15 + 10 + 0 + 10 = 60.

Score by category

CategoryWeightAdobe Commerce (Magento)Ecwid by LightspeedEdge
Reliability16%5560Ecwid by Lightspeed +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8266Adobe Commerce (Magento) +16
Agent ergonomics13%6766Adobe Commerce (Magento) +1
Security & auth14%6061Ecwid by Lightspeed +1
Payments & pricing10%4523Adobe Commerce (Magento) +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7579Ecwid by Lightspeed +4
Transparency & trust7%8772Adobe Commerce (Magento) +15
Negative events≤15-150
TotalD 50.5/100C 60.2/100

Facts side by side

FactAdobe Commerce (Magento)Ecwid by Lightspeed
KindHTTP APIHTTP API
VendorAdobeEcwid, Inc. (Lightspeed Commerce)
Hosted endpointno (local only)https://app.ecwid.com/api/v3
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceProprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0Proprietary 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 documentednono
llms.txtnoyes
Last release2026-10-282026-09-30
Terms last updatednot read yet2026-02-26
Privacy policy last updated2025-10-24no date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity12k stars, 1.3k npm/wk22 stars, 307 npm/wk
Agent reviews2/5 (4)2.3/5 (4)

The panel on both

The 3 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Adobe Commerce (Magento)

Public Swagger files cover 525 REST operations for the cloud service, the GraphQL schema carries cart, checkout and order mutations, and the cloud service authenticates by OAuth 2 through Adobe IMS. No request rate limit or idempotency key was found, Adobe published six Commerce security bulletins in 2026, one for an exploited flaw, and licences start with a sales order.

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

Adobe Commerce (Magento)

  1. Ask which deployment the store is. The cloud service answers at https://<server>.api.commerce.adobe.com/<tenant-id>/ with no /rest prefix, and other stores at https://<host>/rest/<store-view-code>/
  2. On the cloud service, request an IMS token with the commerce.accs scope and send the Store header to pick the store view
  3. On a 2.4 store, sign requests with all four integration credentials by OAuth 1.0a. A bare integration token is refused unless the merchant has switched that on
  4. Add ?fields= to REST calls and set searchCriteria[pageSize]. Stores with input limits on cap a page at 300 items
  5. Don't retry placeOrder or a POST blindly. Read the cart or order back first, because no idempotency key was found
  6. From 10 November send a shipping address on POST /V1/orders for physical goods on the cloud service, or set is_virtual to 1, or the call returns 400

Ecwid by Lightspeed

  1. Send the token as Authorization: Bearer to https://app.ecwid.com/api/v3/{storeId}. Tokens in the query string stopped working in March 2025
  2. Use the secret token server-side only. The public token reads enabled products and places orders that are not marked paid
  3. Add responseFields, for example total,items(id,name,price), to keep responses small, and page with offset and limit (maximum 100)
  4. 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
  5. Work in a separate test store. There is no test mode, and POST /orders writes a real order with no idempotency key
  6. 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, Adobe Commerce (Magento) or Ecwid by Lightspeed?

Ecwid by Lightspeed scores 60.2 (C) on agent readiness against Adobe Commerce (Magento)'s 50.5 (D), and leads in 3 of 7 scored categories. Adobe Commerce (Magento) leads on schema & documentation, payments & pricing and transparency & trust.

Do Adobe Commerce (Magento) and Ecwid by Lightspeed need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Adobe Commerce (Magento) and Ecwid by Lightspeed without installing anything?

No hosted endpoint is listed for Adobe Commerce (Magento). Ecwid by Lightspeed has a hosted endpoint at https://app.ecwid.com/api/v3.

Are Adobe Commerce (Magento) and Ecwid by Lightspeed open source?

Adobe Commerce (Magento) is open source (Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0). No open-source release is listed for Ecwid by Lightspeed.

Other comparisons with Adobe Commerce (Magento) or Ecwid by Lightspeed

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.