# Adobe Commerce (Magento) > Commerce platform from Adobe, built on the open-source Magento core. It runs as Adobe Commerce as a Cloud Service, on Adobe's cloud infrastructure or on the merchant's own servers, and agents reach a store through its REST and GraphQL APIs. - Canonical: https://www.anchorterminal.com/tools/adobe-commerce - Markdown: https://www.anchorterminal.com/tools/adobe-commerce.md (~8,700 tokens) - Slim: https://www.anchorterminal.com/tools/adobe-commerce.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/adobe-commerce.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 63.9/100 · rank #290 of 722 · #9 in Commerce & checkout · not agent-ready · confidence medium** More from Adobe Inc., listed separately because each is its own product: [Adobe Firefly API](https://www.anchorterminal.com/tools/adobe-firefly.md) (Image generation), [Adobe PDF Services / PDF Extract API](https://www.anchorterminal.com/tools/adobe-pdf-extract.md) (Document parsing & extraction), [Adobe Photoshop API](https://www.anchorterminal.com/tools/adobe-photoshop-api.md) (Programmatic asset production). ## Assessment Public Swagger files cover 510 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 in the API documentation, Adobe publishes no MCP server for Commerce, and a licence starts with a sales order. ## Facts | Field | Value | | --- | --- | | Vendor | Adobe Inc. (https://business.adobe.com/products/commerce.html) | | Kind | HTTP API | | Category | Commerce & checkout (https://www.anchorterminal.com/categories/commerce) | | Transport | HTTP | | Auth | OAuth or key · Access comes from the merchant, with no Adobe review of the caller. On Adobe Commerce as a Cloud Service an organisation admin creates an OAuth credential in Adobe Developer Console, and calls carry an Adobe IMS bearer token, from client credentials with the `commerce.accs` scope or from a user flow tied to an Admin role. On Adobe Commerce on Cloud, on-premises and Magento Open Source, the merchant creates an integration limited to chosen ACL resources and requests are signed by OAuth 1.0a. Admin tokens last 4 hours and customer tokens 1 hour by default, and a bare integration token as a bearer token is off by default. | | Pricing | Freemium (Freemium) · No price was read. business.adobe.com timed out on every request on 8 October 2026, and the cloud service licensing terms define an account as one opened under a sales order. No sandbox or trial open without a contract was found in the pages we could read. Magento Open Source, the core with the same REST and GraphQL framework, is free under OSL 3.0, so an owner can start on a self-hosted store with no contract. Its Composer install needs keys from a Commerce Marketplace account. | | x402 | No · No x402, MPP or L402 in the web API docs or the Swagger and GraphQL schemas (checked 2026-10-08). | | Licence | Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0 | | Packages | npm: `@adobe/aio-commerce-sdk` | | Source | https://github.com/magento/magento2 | | Docs | https://developer.adobe.com/commerce/webapi/ | | llms.txt | not found | | Last release | 2026-10-07 | | GitHub stars | 12,198 (as of 2026-10-08) | | npm downloads / week | 1,317 | | Deployments | Adobe Commerce as a Cloud Service (run by Adobe), Adobe Commerce on Cloud, Adobe Commerce on-premises, and the free Magento Open Source core. All use the same web API framework | | REST API | Cloud service 510 operations under `/V1` (Swagger 2.0, version September 2026), admin and integration access only. Release 2.4.9 has 614 admin, 117 customer and 78 guest operations at `https:///rest//V1/` | | GraphQL API | Cloud service 62 queries and 184 mutations at `https://-.api.commerce.adobe.com//graphql`, among them `addProductsToCart`, `applyCouponToCart` and `placeOrder`. Other deployments at `https:///graphql` | | Auth | Cloud service by OAuth 2 through Adobe IMS (client credentials with the `commerce.accs` scope, or a user flow). Other deployments by integration with OAuth 1.0a signing, admin tokens (4 hours) and customer tokens (1 hour) | | Permissions | ACL resources chosen per integration or Admin role. No read-only mode found | | Limits | Input limits (20 items in a list input, 5,000 asynchronous, 300 a page) are off by default on 2.4 stores. GraphQL complexity 300 and depth 20. No request rate limit found. Payment endpoints can be rate limited from 2.4.7 | | Response size | `?fields=` on REST, field selection in GraphQL, `searchCriteria[pageSize]` and `searchCriteria[currentPage]` on lists | | Bulk and async | Asynchronous and bulk endpoints for POST, PUT and DELETE return a bulk UUID, with status at `/V1/bulk/:bulkUuid/status` | | SDKs | `@adobe/aio-commerce-sdk` 2.0.0 on npm (Apache-2.0) for App Builder apps. No client library in a second language found | | MCP server | None from Adobe for Commerce found. Experience League's llms.txt lists MCP servers for AEM only | | Releases | Cloud service releases in August, twice in September and on 7 October 2026. 2.4.9 on 12 May 2026, with a patch each May and security patches between | | Support window | Three years of standard support for each release. 2.4.9 to 31 May 2029, 2.4.8 to 31 May 2028, 2.4.7 to 31 May 2027 | | Status | status.adobe.com lists Adobe Commerce with components by deployment and region. A self-hosted store has no vendor status | | SLA | The Unified SLA's Actionability Addendum (23 July 2026) covers Adobe Commerce. Percentage not read | | Data on termination | Cloud service customer data is kept for the licence term, with 30 days to export after it ends, per the 2025v1 licensing terms | | Sub-processors | Seven named for Adobe Commerce on the list updated 28 September 2026, among them Microsoft, Snowflake, MongoDB, New Relic, Platform.sh, SendGrid and Fastly, in the USA, EU and other regions | | Capabilities | commerce.products, commerce.orders, commerce.cart, commerce.checkout, commerce.headless | | Tags | hosted, self-hosted, enterprise, open-source, openapi, graphql, oauth, php, sales-led, status-page, bug-bounty, b2b | | JSON | https://www.anchorterminal.com/api/v1/tools/adobe-commerce.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 55 | 11.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 82 | 13.3 | | Agent ergonomics | 13% | 16.2 | 67 | 10.9 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 80, provenance 99) | 7% | 8.8 | 90 | 7.9 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.9 → B** | ### Why each score - Reliability 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 (20). Its event feed shows eight Commerce events between 1 and 23 September 2026, three marked major. Catalogue Service, Live Search and the Admin panel had 2 hours 10 minutes of availability and performance trouble on 1 September, Live Search 45 minutes on 2 September, and Commerce Admin and provisioning on the cloud service 1 hour 39 minutes on 18 September. None names the REST or GraphQL endpoint itself, so 5 of 30 where several majors would score 0 (5). 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), but no request rate limit was found (5). The server-to-server sample retries on 429 after `retry-after`, with no written guidance and no idempotency keys found (5). The Unified SLA's Actionability Addendum of 23 July 2026 covers Adobe Commerce. We didn't read the percentage (10). Generally available (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 82: Swagger 2.0 YAML files in the public docs repository for the cloud service (510 operations, version September 2026) 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 510 cloud service operations carry a description, with a median length of 39 characters and 147 under 30, and 239 of 246 GraphQL queries and mutations have one. 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, 401 and 500 responses in the spec, with no list of error codes (11). A schema per release, monthly cloud service release notes and release notes for each 2.4 version (15). - Agent ergonomics 67: `?fields=` trims any REST response and GraphQL returns only the fields asked for. The surface is large, at 510 REST operations and 246 GraphQL queries and mutations on the cloud service (23). `searchCriteria` gives filters with comparison operators such as `eq`, `in` and `like`, sort orders, `pageSize` and `currentPage`, and GraphQL lists page the same way (20). REST errors are an HTTP code and a message with parameters. GraphQL answers 200 for business errors with a message and a category, and no stable list of codes was found (12). No idempotency keys found. Asynchronous and bulk endpoints return a bulk UUID whose status can be read back, and PUT by SKU updates in place (6). List calls need the long `searchCriteria` syntax, 2.4 stores need OAuth 1.0a signing, and the only official client library is `@adobe/aio-commerce-sdk` for JavaScript (6). - Security & auth 60: The cloud service takes OAuth 2 tokens from Adobe IMS, by client credentials with the `commerce.accs` scope or by a user flow tied to an Admin role. A 2.4 store issues integrations whose requests are signed by OAuth 1.0a, admin tokens that last 4 hours and customer tokens that last 1 hour, and bare integration tokens as bearer tokens are off by default. No secret in a URL was found. Scopes stop at the product level, so finer limits come from roles (26). Each integration or admin role is limited to chosen ACL resources. No read-only switch or confirmation step for writes was found (12). The APIs return shopper-written text such as names, order comments and reviews, and no prompt-injection guidance was found (0). Action Logs record admin users' changes with user, IP address and date on Adobe Commerce, not on Magento Open Source. Whether integration calls are logged wasn't established (8). security.txt is valid to 30 July 2027 and names a public Intigriti programme and PSIRT, and security patches are tied to numbered bulletins. The compliance list didn't show its Commerce rows to our reader (14). - Payments & pricing 30: No x402, MPP or L402 in the API docs or the schemas (0). business.adobe.com timed out on every request on 8 October 2026, 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). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75: The cloud service's latest production release is dated 7 October 2026 (30). Four cloud service releases since August 2026, in August, twice in September and in October. The 2.4 line last shipped on 12 May 2026 with 2.4.9 and security patches for 2.4.6 to 2.4.8 (20). The API docs repository merged pull requests on 8 October 2026. magento/magento2 has 1,230 open issues and we couldn't read how recent the replies are, because the GitHub API refused us for its rate limit (12). `@adobe/aio-commerce-sdk` is at 2.0.0 with alpha builds published on 8 October 2026. It is for App Builder and JavaScript only, and no Adobe Commerce server is in the official MCP registry (8). The docs repository carries tests and link checks. CI on the core repository wasn't read (5). - Transparency & trust 90: 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/adobe-commerce.md (JSON https://www.anchorterminal.com/fixes/adobe-commerce.json) ### What we couldn't check - unchecked: the pricing page at business.adobe.com/products/commerce/pricing.html, which timed out on every request, so no price, trial or sandbox offer was read and Payments scores it as absent - unchecked: the security bulletins at helpx.adobe.com (APSB26-05 and APSB26-49 among them), which answered 403, so severities and any exploitation in the last 12 months weren't read and no deduction was considered - unchecked: which certifications Adobe lists for Adobe Commerce. The compliance list didn't show its product rows to our reader - unchecked: the uptime percentage and credits in the Unified SLA and its Actionability Addendum, and the text of the General Terms and the data processing addendum - unchecked: how quickly issues on magento/magento2 get a reply, and whether its CI passes. The GitHub API refused us for its rate limit - No request rate limit for the cloud service's REST or GraphQL APIs was found in the reviewed documentation - Whether calls made by an integration appear in Action Logs wasn't established - The sub-processor list names Microsoft for hosting, while the status page's registry lists Commerce Cloud regions on AWS, Azure and GCP ### Sources - Commerce web API docs index, as Markdown: (seen 2026-10-08) - API docs repository at its commit of 8 October 2026 (Swagger files in `src/openapi`, GraphQL schema JSON in `spectaql`, REST, GraphQL and authentication pages): (seen 2026-10-08) - REST overview (deployments, URL structure, first request): (seen 2026-10-08) - cloud service REST authentication: (seen 2026-10-08) - server-to-server authentication: (seen 2026-10-08) - token-based authentication on 2.4 stores: (seen 2026-10-08) - input limiting: (seen 2026-10-08) - payment rate limiting: (seen 2026-10-08) - GraphQL security configuration: (seen 2026-10-08) - status codes and responses: (seen 2026-10-08) - filtered responses: (seen 2026-10-08) - cloud service release notes: (seen 2026-10-08) - cloud service overview: (seen 2026-10-08) - shared responsibility model: (seen 2026-10-08) - released versions: (seen 2026-10-08) - lifecycle policy: (seen 2026-10-08) - patch release schedule: (seen 2026-10-08) - security patch notes for 2.4.8: (seen 2026-10-08) - Composer install guide: (seen 2026-10-08) - Action Logs: (seen 2026-10-08) - Experience League llms.txt: (seen 2026-10-08) - status page: (seen 2026-10-08) - status event feed the status page loads: (seen 2026-10-08) - product terms index: (seen 2026-10-08) - General Terms page: (seen 2026-10-08) - licensing terms for Adobe Commerce as a Cloud Service (2025v1): (seen 2026-10-08) - service commitments (SLA documents): (seen 2026-10-08) - data protection terms page: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - sub-processor list: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - core repository (licence, stars, releases): (seen 2026-10-08) - npm package: (seen 2026-10-08) - MCP registry search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 99/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Adobe Inc. | 20/20 | | Domain age | adobe.com, registered 1986-11-17 (39 years) | 15/15 | | Endpoint on the vendor's domain | adobe.com | 15/15 | | Terms of service | published | 10/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.adobe.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The privacy policy, last updated 24 October 2025, names Adobe Inc. as controller in the US, Adobe KK in Japan and Adobe Systems Software Ireland Limited elsewhere. The terms link is Adobe's General Terms 2025v1, effective 3 October 2025, as given on the enterprise licensing page. We read that page and the product-specific terms for Adobe Commerce as a Cloud Service (2025v1, 13 October 2025), not the General Terms PDF itself. Separate product-specific terms cover Adobe Commerce on Cloud (18 February 2025), on Managed Services (18 March 2025) and on-premise software (9 January 2023). The privacy policy says Adobe is the processor for enterprise products and that it doesn't apply to data enterprise customers collect. A data processing addendum is published at www.adobe.com/cc-shared/assets/pdf/legal/terms/enterprise/pdfs/dpa-ww.pdf. Cloud service endpoints are on api.commerce.adobe.com. Stores on Adobe Commerce on Cloud, on-premises and Magento Open Source answer on the merchant's own domain. security.txt at www.adobe.com is PGP-signed, expires 30 July 2027 and names an Intigriti programme and psirt@adobe.com. www.adobe.com and helpx.adobe.com answered curl with 403. The legal pages were read through WebFetch, and the helpx security bulletins weren't read at all. Verisign RDAP gives a registration date of 1986-11-17 for adobe.com. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.adobe.com/cc-shared/assets/pdf/legal/terms/enterprise/pdfs/generalterms-na-2025v1.pdf), not read yet. **Privacy policy** (https://www.adobe.com/privacy/policy.html), read 2026-10-08, dated 2025-10-24, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "In some cases, in order to show you more relevant ads, we disclose with social media platforms and other advertising partners, information about actions you take on our websites and apps, such as which pages you visit and which ads you saw." - Gives the date it was last updated. Last updated 2025-10-24. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). Insights from analytics on cloud content may inform Adobe marketing to the user, subject to opt-out rights. "Insights from Content Analytics may be used to inform our marketing to you, subject to your opt-out rights regarding our marketing." - Also in the text (2026-10-08). Cloud content may be scanned automatically for illegal or abusive material, with human review when content is flagged or reported. "Human review may occur when your Cloud Content is flagged or reported as illegal or abusive." - Also in the text (2026-10-08). Adobe may give personal information to a business when the user signs in with that business email domain or was invited by that business. "If you are using an email address that is associated with a business domain (e.g., yourname@businessname.com) to access Adobe's Services and Software, or if you were invited to use the Services and Software by a business, we may provide your personal information to that business." ## Live (updated 2026-10-08 19:38 UTC) - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/adobe-commerce.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Magento Open Source | free | per month (plan) | OSL 3.0 core, you pay for your own hosting. Adobe Commerce prices weren't read | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Swagger 2.0 files for the cloud service (510 operations) and for releases 2.4.6 to 2.4.9 sit in the public docs repository - The cloud service takes OAuth 2 client credentials or user tokens from Adobe IMS, and older bearer integration tokens are off by default on 2.4 stores - `?fields=` trims any REST response, and `searchCriteria` filters, sorts and pages every list endpoint - Cloud service release notes list four production releases between August and 7 October 2026, each naming new endpoints - A lifecycle policy gives end-of-support dates for every 2.4 release line, and the sub-processor list was updated on 28 September 2026 ## Weaknesses - No request rate limit for the REST or GraphQL APIs was found in the reviewed documentation, and 429 handling appears only in a code sample - No idempotency keys were found, so a retried POST can create a second order or cart item - status.adobe.com lists three Commerce incidents marked major in September 2026, two of them longer than an hour - The cloud service drops the customer and guest REST APIs, so shopping flows there go through GraphQL only - No Adobe MCP server for Commerce was found, and the only official client library is a JavaScript package for App Builder ## Before you call it (notes for agents) 1. Ask which deployment the store is. The cloud service answers at `https://.api.commerce.adobe.com//` with no `/rest` prefix, and other stores at `https:///rest//` 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 ## Connect First request: ```bash curl --location 'https://.api.commerce.adobe.com//' \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --header 'Store: >' ``` Through letme (picks today, calling later): https://letme.dev/adobe-commerce. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Shopify API + MCP | BB | 75 | 52 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/shopify.md | | WooCommerce API + MCP | BB | 72.9 | 84 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/woocommerce.md | | Shopware | BB | 71.4 | 112 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/shopware.md | | commercetools | BB | 71.3 | 116 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/commercetools.md | | Vendure | BB | 70.9 | 123 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/vendure.md | | Square | B | 69.2 | 166 | commerce.products, commerce.orders, commerce.checkout, commerce.cart, commerce.headless | no | https://www.anchorterminal.com/tools/square.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Three deployments share one API framework. The cloud service answers at `https://.api.commerce.adobe.com//` and drops the customer and guest REST APIs, which stay available through GraphQL (source: ) - The cloud service release of 7 October 2026 added REST endpoints for catalogue price rules, custom cart item prices and shipping discounts (source: ) - Input limits are off by default on 2.4 stores. When on, a list input takes 20 items, an asynchronous one 5,000, and a page 300 (source: ) - GraphQL queries are capped at a complexity of 300 and a depth of 20 by default (source: ) - status.adobe.com's event feed shows eight Adobe Commerce events between 1 and 23 September 2026, three marked major (source: ) - Adobe Commerce 2.4.9 was released on 12 May 2026 with standard support to 31 May 2029, and Cloud environments on unsupported versions lose traffic from 1 June 2027 (source: ) - No Adobe Commerce server from Adobe is in the official MCP registry. The entries that name it are third parties' (source: ) ## Compare - [Adobe Commerce (Magento) vs BigCommerce API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-bigcommerce.md): B 63.9 vs B 64.3 - [Adobe Commerce (Magento) vs Commerce Layer API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-commerce-layer.md): B 63.9 vs B 63.7 - [Adobe Commerce (Magento) vs commercetools](https://www.anchorterminal.com/compare/adobe-commerce-vs-commercetools.md): B 63.9 vs BB 71.3 - [Adobe Commerce (Magento) vs Ecwid by Lightspeed](https://www.anchorterminal.com/compare/adobe-commerce-vs-ecwid.md): B 63.9 vs B 63.2 - [Adobe Commerce (Magento) vs Elastic Path API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-elastic-path.md): B 63.9 vs D 50.1 - [Adobe Commerce (Magento) vs Medusa API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-medusa.md): B 63.9 vs B 63.5 - [Adobe Commerce (Magento) vs Saleor API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-saleor.md): B 63.9 vs B 68.6 - [Adobe Commerce (Magento) vs Shopify API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-shopify.md): B 63.9 vs BB 75 - [Adobe Commerce (Magento) vs Shopware](https://www.anchorterminal.com/compare/adobe-commerce-vs-shopware.md): B 63.9 vs BB 71.4 - [Adobe Commerce (Magento) vs Snipcart API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-snipcart.md): B 63.9 vs E 40.8 - [Adobe Commerce (Magento) vs Square](https://www.anchorterminal.com/compare/adobe-commerce-vs-square.md): B 63.9 vs B 69.2 - [Adobe Commerce (Magento) vs Swell](https://www.anchorterminal.com/compare/adobe-commerce-vs-swell.md): B 63.9 vs C 55 - [Adobe Commerce (Magento) vs Vendure](https://www.anchorterminal.com/compare/adobe-commerce-vs-vendure.md): B 63.9 vs BB 70.9 - [Adobe Commerce (Magento) vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/adobe-commerce-vs-wix.md): B 63.9 vs C 61.4 - [Adobe Commerce (Magento) vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/adobe-commerce-vs-woocommerce.md): B 63.9 vs BB 72.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on adobe.com or one of its subdomains, or the README of github.com/magento/magento2. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "adobe-commerce", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Adobe Commerce (Magento) on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Adobe Commerce (Magento) on Anchor Terminal](https://www.anchorterminal.com/badges/adobe-commerce.svg)](https://www.anchorterminal.com/tools/adobe-commerce) ``` Plain link: ```html Adobe Commerce (Magento) on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Adobe Commerce (Magento) is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/adobe-commerce-dark.png - Light: https://www.anchorterminal.com/assets/share/adobe-commerce-light.png