# Adobe Commerce (Magento) (slim) > 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. - Full: https://www.anchorterminal.com/tools/adobe-commerce.md (~8,700 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/tools/adobe-commerce.json · canonical https://www.anchorterminal.com/tools/adobe-commerce - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08 **B · 63.9/100 · rank #290 of 722 · #9 in Commerce & checkout · not agent-ready · confidence medium** 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 - Kind: HTTP API · vendor: Adobe Inc. · category: Commerce & checkout · legal entity: Adobe Inc. · provenance 99/100 - Local only (HTTP): npm `@adobe/aio-commerce-sdk` - Auth: OAuth or key · pricing: Freemium · x402: no · licence: Proprietary for Adobe Commerce under Adobe's General Terms and product-specific licensing terms. The Magento Open Source core is OSL 3.0 - Probe metrics: not measured yet (probes haven't run) - 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 - Prices: Magento Open Source free per month (plan) - Scores: Reliability 55, Performance pending, Schema & documentation 82, Agent ergonomics 67, Security & auth 60, Payments & pricing 30, Task success pending, Maintenance & community 75, Transparency & trust 90 · total over the 7 assessed categories - Why: Reliability, Graded with the hosted lines, because Adobe runs the cloud service and Adobe Commerce on Cloud. · Schema & documentation, Swagger 2.0 YAML files in the public docs repository for the cloud service (510 operations, version September 2026) and for the admin, custo… · Agent ergonomics, `?fields=` trims any REST response and GraphQL returns only the fields asked for. · Security & auth, 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 Adm… · Payments & pricing, No x402, MPP or L402 in the API docs or the schemas (0). · Maintenance & community, The cloud service's latest production release is dated 7 October 2026 (30). · Transparency & trust, Magento Open Source is OSL 3.0. Adobe Commerce is proprietary under Adobe's General Terms (2025v1, 3 October 2025) and a product-specific do… - Sources: 35, open questions: 8, both in the full twin - Capabilities: commerce.products, commerce.orders, commerce.cart, commerce.checkout, commerce.headless - JSON: https://www.anchorterminal.com/api/v1/tools/adobe-commerce.json - Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/adobe-commerce.svg` or a link to https://www.anchorterminal.com/tools/adobe-commerce from a page on adobe.com or one of its subdomains, or the README of github.com/magento/magento2, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin. ## Before you call it 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 ```bash curl --location 'https://.api.commerce.adobe.com//' \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --header 'Store: >' ``` Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/adobe-commerce ## Similar tools | Tool | Grade | Score | Shared capabilities | Slim | | --- | --- | --- | --- | --- | | Shopify API + MCP | BB | 75 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | https://www.anchorterminal.com/tools/shopify.min.md | | WooCommerce API + MCP | BB | 72.9 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | https://www.anchorterminal.com/tools/woocommerce.min.md | | Shopware | BB | 71.4 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | https://www.anchorterminal.com/tools/shopware.min.md | | commercetools | BB | 71.3 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | https://www.anchorterminal.com/tools/commercetools.min.md | | Vendure | BB | 70.9 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | https://www.anchorterminal.com/tools/vendure.min.md | ## Panel reviews (0, desk reviews from public material, no calls made)