Can AI agents automate Adobe Commerce?

Adobe Commerce, formerly Magento, is automatable today through documented Web APIs. One record covers both editions because the surfaces differ. Adobe Commerce on Cloud, on-premises, and Magento Open Source (PaaS) expose REST at https://<host>/rest/<store>/ plus GraphQL at https://<host>/graphql and SOAP. PaaS third-party integrations authenticate with OAuth 1.0a (consumer key, consumer secret, access token, token secret). Mobile and Admin or customer callers use token-based Bearer credentials from username-password token services; Admin tokens require two-factor authentication. Adobe Commerce as a Cloud Service (SaaS) uses a smaller REST subset without customer or guest REST; similar storefront work uses GraphQL. Cloud Service REST requires Adobe IMS OAuth 2. Traditional admin and integration token generation is not supported on SaaS. Server-to-server IMS uses client_credentials against ims-na1.adobelogin.com/ims/token/v3 with the commerce.accs scope; user authentication is a separate IMS OAuth flow. GraphQL includes queries and mutations, including generateCustomerToken. Official Admin UI SDK is JavaScript/React for App Builder Admin extensions, not a REST client. PaaS installs include bin/magento for setup, cache, index, and configuration. Adobe documents Commerce webhooks for PaaS (webhooks.xml) and Cloud Service (Admin or REST subscribe). The older Getting Started page still says the web API framework does not support webhooks; the dedicated webhook guide is the current event path. Adobe's opened Experience League llms.txt lists Commerce docs and AEM MCP servers, not a Commerce MCP server. First-party MCP ownership is therefore unknown. Connector catalogs were not opened. Computer-use viability is unassessed. API scores 8 and is the best path because REST and GraphQL are documented with authentication on both editions; the edition split and Cloud Service REST subset keep the score below 9.

Best path today: api · Overall automatability: 8/10