Mapping Agentic AI Protocols to the OSI Stack: What Fits, What Doesn't

2026-07-06 · Source: HackerNoon · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Robotics & Autonomous Systems · Depth: Intermediate, medium

Summary

Current agentic AI protocols, including Anthropic's MCP, Google's A2A, IBM's ACP, AG-UI, and ANP, are analyzed by mapping them to the 1984 OSI Reference Model to understand their structure and identify architectural gaps. Many agent protocols align with OSI layers, reusing existing web infrastructure for layers 1 and 2, and handling addressing/discovery (layer 3) and task lifecycle tracking (layer 4) similarly to traditional networking. However, agentic AI introduces new requirements not covered by OSI, specifically Identity, Payment, and Governance. Identity, addressed by ANP's DIDs, and Payment, with proposals reusing HTTP 402, are emerging. Governance remains the least developed, lacking clear accountability for agent actions. This dual development path sees some protocols like MCP achieving rapid adoption, while others are still in the conceptual stage.

Key takeaway

For AI Architects designing agentic systems, understanding the OSI-like structure of current protocols is crucial. You should prioritize protocols that address identity (e.g., DIDs), payment (e.g., HTTP 402), and especially governance, as these are critical gaps in existing models. Integrating these new requirements early will prevent future fragmentation and ensure robust, accountable agent interactions. Evaluate protocols like MCP for immediate adoption, while actively contributing to solutions for the unsettled layers.

Key insights

Agentic AI protocols can be mapped to the OSI model, but require new layers for identity, payment, and governance.

Principles

• Protocol layering enables separation of concerns.
• Agentic AI needs built-in identity and payment.
• Governance for agent actions is a critical gap.

Method

The article maps agent protocols (MCP, A2A, ACP, AG-UI, ANP) to the OSI stack layer by layer, identifying alignments and unique requirements for agentic AI.

In practice

• Use existing web infrastructure for agent transport.
• Implement DIDs for decentralized agent identity.
• Consider HTTP 402 for agent-to-agent payments.

Topics

• Agentic AI Protocols
• OSI Reference Model
• Decentralized Identifiers
• Agent Governance
• Machine-to-Machine Payment
• Protocol Layering

Best for: CTO, VP of Engineering/Data, AI Product Manager, AI Architect, AI Engineer, Director of AI/ML

Related on AIssential

• Governance Gaps in Agent Interoperability Protocols: What MCP, A2A, and ACP Cannot Express — Current agent interoperability protocols are insufficient for enterprise-level governance, requiring a new architectural layer.
• Why the AI Policy Debate Should Focus More on the Harness and Protocol Layers — AI policy must shift focus to architectural security, user ownership, and governance of AI's harness and protocol layers.
• The Agentic AI Governance Stack Got Built This Year - Here Is the Part No Vendor Can Ship — The agentic AI governance infrastructure is built, but human judgment and accountability remain critical.
• The Missing Mechanisms of the Agentic Economy — Protocols, workflows, and agent skills are "engineered arguments" that shape markets and enable decentralized agentic economies.
• The DevOps guide to governing and managing agentic AI at scale — Autonomous AI agents demand integrated governance across their lifecycle to ensure reliability, security, and compliance.
• How can enterprises govern MCP connections at scale? — MCP connections, enabling autonomous agent actions, demand robust governance to mitigate significant enterprise risks.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by HackerNoon.