AgentsThe story, in brief

Presentation: APIs for Agents: Rethinking API Programs in the MCP Era

Morgan Stanley built the API infrastructure for agent-to-agent commerce. Here's how they scaled it without breaking production.

Illustration of independent geometric mechanisms passing paper tasks along branching amber tracks.
AI agents and the coordination of work.AI illustration by KeyNews
The KeyNews take

Why it matters

Enterprise agents aren't a prototype problem anymore—they're a platform problem. This is how a major financial institution engineered governance, safety, and scale for multi-agent workflows in production.

The key facts

10 to know
  1. Morgan Stanley integrating Model Context Protocol (MCP) and Agent-to-Agent (A2A) communications

  2. Architecture as Code with CALM for API governance automation

  3. Deployment gates enforcing automated governance for agent workflows

  4. Zero-downtime platform upgrades for agentic systems at scale

  5. Enterprise agents across multiple workflows (implied scale beyond pilot)

  6. Morgan Stanley uses Architecture as Code (CALM) to modernize API program

  7. Integration of Model Context Protocol (MCP) and Agent-to-Agent (A2A) communications

  8. Automated governance enforcement through deployment gates

  9. Zero-downtime platform upgrades for agentic workflows

  10. Focus on safe scaling of enterprise AI and agents

Go to the source

InfoQ AI/MLinfoq.com

Publisher excerpt: Jim Gough and Andreea Niculcea explain how Morgan Stanley uses Architecture as Code with CALM to modernize its API program. They demonstrate integrating Model Context Protocol (MCP) and Agent-to-Agent (A2A) communications, enforcing automated governance through deployment gates, and executing…
Read original report
Back to today's editionMore agents news

Keep reading

Related stories

More from Agents