The Protocol of Doing: Why "Chat" is Over and "Agency" Has Begun

Wed, 24 Dec 2025 03:39:31 +0000

Introduction: The "Doing Problem"
We have officially exited the "Chat Phase" of AI. For the past two years, we treated LLMs like brilliant consultants trapped in a glass box—great at answering questions, writing poetry, or debugging snippets. But the moment we asked them to do something—log into SAP, update a PO, or restart a server—the architecture collapsed.

We hit the "Doing Problem."

LLMs are born context-blind. They don't know your schema, your security policies, or that your legacy mainframe requires a specific correlation ID header. To fix this, developers started hardcoding fragile "tools" into their agents, creating a maintenance nightmare.

The solution isn't better prompts; it's better architecture. We need a "TCP/IP moment" for AI—a standard way for intelligence to connect to infrastructure.

The Missing Piece: A "Global Catalog" for AI
If you want an agent to act safely, you can't just give it an API key and hope for the best. You need a Global Catalog—essentially a DNS for enterprise capability.

Instead of an agent guessing how to interact with your systems, it queries a centralized metadata layer.

Agent: "I need to update a customer address."
Catalog: "I have a Salesforce Update Action and an SAP Customer BAPI.
Here are the schemas and the required permission scopes for both."

This solves the N×M Integration Problem (N models connecting to M tools). By standardizing the metadata of actions and triggers, you create a unified interface. The agent doesn't need to know the specifics of the SAP BAPI; it only needs to know the Catalog Schema.

The "Immune System": Why You Need an AI Gateway
Deploying agents without a governance layer is a security disaster waiting to happen. This is the "Shadow AI" crisis: junior devs calling OpenAI directly from production services, potentially leaking PII.

A robust AI Gateway acts as a reverse proxy for intelligence, handling:

Rate Limiting: Prevents "loops of death" where two agents argue and rack up a $50k bill.
Response Caching: Serves repeated answers from memory to slash API costs.
PII Redaction: Automatically detects and masks sensitive data (like SSNs) before it ever leaves your perimeter.

The Mechanics of Execution
To make agents actually work, we need to move beyond "text-in, text-out" and focus on the "hands" of the system:

Flow Services as APIs: Logic should be decoupled from the agent. The agent shouldn't write the SQL query; it should call a deterministic Flow Service that handles the query safely.

Private Network Connections: Your agent needs to reach "dark data"—resources sitting inside private VPCs or on-prem data centers—without traversing the public internet.

Conclusion: The Boring Revolution
The future of AI isn't just about smarter models; it's about boring, reliable plumbing. It's about LDAP integration, metadata synchronization, and private network links.

We don't need another chatbot. We need a nervous system. We need a way to tell an AI, "Fix the supply chain bottleneck," and have it strictly, securely, and correctly identify the endpoint, authenticate, and execute the fix—all while being governed by a central platform.

For a full technical deep dive into how IBM webMethods is implementing this architecture, read my original article: The Protocol of Doing.

How Agentic AI Is Changing Integration Workflows

Fri, 17 Oct 2025 23:55:45 +0000

Integration Workflows Are Evolving
In today’s IT landscape, integration isn’t just about connecting systems—it’s about enabling workflows that are adaptive, scalable, and intelligent. As hybrid IT environments grow more complex, traditional integration methods are struggling to keep up with demands for flexibility, security, and performance.

Enter Agentic AI and the Agent Mesh, a distributed architecture powered by autonomous AI agents. Together, these technologies are redefining integration workflows by enabling smarter collaboration between systems and proactive optimization of processes. Whether you’re managing APIs, securing data exchanges, or scaling workflows across hybrid environments, the Agent Mesh offers a groundbreaking path forward.

For a deeper dive into the Agent Mesh concept, check out:
The Agent Mesh: Building Smarter Integration Workflows with AI Agents

Agent Mesh: The Integration Renaissance

What Makes the Agent Mesh Different?

The Agent Mesh isn’t just a new integration tool—it’s an architectural shift. Unlike traditional centralized platforms, the Agent Mesh operates as a distributed network of AI agents, with each agent specializing in specific tasks. By collaborating dynamically, these agents can adapt to changes in real time, ensuring workflows remain efficient and resilient.

Here’s how the Agent Mesh improves integration workflows:

Distributed Intelligence: Each agent operates independently while sharing insights across the mesh, optimizing workflows collectively.
Resilience: If one agent encounters an issue, others adapt and maintain operations seamlessly.
Proactive Optimization: Agents monitor data flows continuously, identifying inefficiencies and refining workflows without manual intervention.
Security at Scale: The distributed nature of the mesh reduces single points of failure, ensuring secure data exchanges across hybrid environments.

Technical Implementation Details

1. Core Technologies for Building the Agent Mesh

To implement the Agent Mesh, you’ll need tools and protocols that support distributed collaboration between AI agents. Here are a few essential components:

IBM WebMethods Hybrid Integration (IWHI):
IWHI provides the backbone for connecting diverse systems, including APIs, legacy databases, and cloud platforms. It offers:
- API Management: Seamlessly integrate systems through secure APIs.
- B2B Workflows: Simplify external system collaboration with scalable business workflows.
- Predictive Analytics: Monitor and optimize workflows using AI-powered insights.
Agent Communication Protocol (ACP):
ACP is the foundation of the Agent Mesh, enabling AI agents to exchange data, collaborate, and refine workflows dynamically.
- Implementation Steps:
  1. Configure ACP endpoints within IWHI to establish secure communication between agents.
  2. Use encryption protocols (e.g., WS-Security) to ensure data integrity during agent collaboration.
  3. Deploy monitoring tools to analyze ACP traffic and optimize agent interactions.

For more on how ACP fits into the Agent Mesh, check out:
Agent Mesh: The Integration Renaissance

2. Protocols for Secure and Scalable Integration

Specialized protocols ensure that workflows within the Agent Mesh are secure, reliable, and scalable. Here’s how they fit into your implementation strategy:

MCP (Message Control Protocol):
MCP ensures fault-tolerant messaging across distributed systems, making it ideal for workflows requiring message integrity.
- Implementation Tip: Configure MCP message queues within IWHI to handle high volumes of traffic without bottlenecks.
A2A (Application-to-Application Protocol):
A2A facilitates direct communication between applications, enabling faster data exchanges and reducing latency.
- Implementation Tip: Use middleware to connect legacy systems with A2A protocols for seamless integration.
ACP (Agent Communication Protocol):
ACP allows AI agents to exchange data and collaborate within the mesh.
- Implementation Tip: Deploy ACP alongside IWHI to enable agents to coordinate tasks like API orchestration and data pipeline management.

3. Real-World Example: Retail Integration

Scenario: A retailer needs to unify inventory tracking across e-commerce platforms, warehouses, and logistics systems.

Solution:

Use IBM WebMethods Hybrid Integration to connect APIs between systems.
Deploy AI agents using ACP Protocol to monitor inventory levels, predict stock shortages, and automate reordering workflows.
Implement MCP to ensure reliable messaging between agents and systems, even during peak traffic periods.
Add layers of security with OAUTH or other protocols to protect sensitive inventory and logistics data.

Why This Matters

The Agent Mesh is more than just a technical innovation—it’s a strategic necessity for organizations seeking to thrive in the modern IT landscape. By leveraging AI agents and distributed architectures, businesses can:

Scale workflows efficiently without disruptions.
Secure data exchanges across diverse systems.
Adapt to changing demands in real
time.

For a deeper dive into these concepts, explore:
The Agent Mesh: Building Smarter Integration Workflows with AI Agents