Can AI agents automate IBM Maximo Application Suite?

IBM Maximo Application Suite is automatable today through Maximo Manage REST and OSLC APIs on object structures such as MXAPIASSET. Agents query with oslc.select and oslc.where, create with POST, and update with PATCH or MERGE against /oslc or /api collection URIs. Maximo Manage generates tenant OpenAPI 3 (OAS3) Swagger from those object structures. For Maximo Application Suite, IBM documents API-key authentication as the headless path: keys are bound to a Maximo user, inherit that user's permissions, and must be sent on every request because they do not create a server session. Interactive suite login uses SAML or OIDC; older Maximo Asset Management MAXAUTH, BASIC, and FORM logins are documented as unsupported for Maximo Manage. The same API stack is reached at /maximo/api when application-server security protects /oslc. The Maximo Integration Framework adds object structures, publish channels, enterprise services, HTTP and scripted endpoints, and Kafka or JMS providers. REST export and import support JSON and CSV; Manage also loads XML and flat files. Those surfaces are tenant-configured: object structures must be API-eligible, keys and security groups must be granted, and Maximo Public SaaS additionally blocks object-structure edits, XML, web services, and integration scripting while routing outbound events to customer-owned Kafka. The official MAS CLI installs, updates, backs up, and gathers logs on OpenShift; it is not a business transaction client. Two maintained third-party MCP servers target Maximo, but IBM has not declared a first-party server. Named Zapier, Make, Power Automate, and n8n connectors were not present in the catalogs checked. Computer-use viability is unassessed. This record covers Maximo Application Suite and Maximo Manage, not TRIRIGA, not Maximo Spatial as a standalone GIS product, and not IBM i 5250.

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