222 The Agent Interoperability Landscape: Standards, Consolidation, and the Agent Stack

222.1 1. Introduction

The three preceding chapters examined MCP, A2A, and AP2 individually. This chapter steps back to survey the entire field of agent-interoperability standards as it stood in early 2026, and, more importantly, to explain the shape the field took. The story of 2025 is not a proliferation of competing protocols but a rapid consolidation of them: a movement from a sprawl of overlapping specifications toward a layered, “complementary-not-competing” stack, with the Linux Foundation emerging as the dominant neutral steward. Understanding that consolidation is more durable knowledge than memorizing any single protocol, because it tells you how to reason about the next standard that appears.

We proceed in three passes: a brief recap of the major protocols organized by the layer each occupies; a comparison of the broader field including the standards that lost, merged, or remain niche; and an analysis of the consolidation dynamic itself, culminating in the December 2025 formation of the Agentic AI Foundation.

222.2 2. The Agent Stack

The mental model that crystallized over 2025 is a stack of layers, each protocol owning a distinct concern:

flowchart TD
    L1["Content access: NLWeb, websites and agents"]
    L2["Commerce: AP2 plus x402, agents move money"]
    L3["Agent to agent: A2A, peers discover and delegate"]
    L4["Agent to tools: MCP, tools, resources, data"]
    L5["Multi-agent infra: AGNTCY/OASF, directory, identity, obs"]
    L1 --> L2 --> L3 --> L4 --> L5

A useful one-line summary: MCP connects an agent downward to tools; A2A connects agents sideways to peers; AP2 sits above to move money; and infrastructure projects such as AGNTCY and content layers such as NLWeb provide the directory, identity, and content-access scaffolding around them. These are not rivals fighting for the same slot, they compose.

222.2.1 2.1 MCP, Model Context Protocol (recap)

Created by Anthropic and open-sourced in November 2024, MCP is the vertical layer: a single agent’s connection to external tools, data, and resources, often described as “the USB-C port for AI.” It uses JSON-RPC 2.0 over stdio (local) and Streamable HTTP (remote, which superseded the earlier HTTP+SSE transport), and exposes three primitives, tools, resources, and prompts, from an MCP server to an MCP client. Anthropic introduced a formal governance model in July 2025 (Specification Enhancement Proposals and a maintainer steering group), Microsoft and OpenAI joined the steering committee in 2025, and on December 9, 2025, MCP became a founding project of the Agentic AI Foundation. It is the most mature and widely adopted of all these standards, with well over ten thousand published servers and support across every major assistant.

222.2.2 2.2 A2A, Agent2Agent (recap)

Created by Google (April 2025) and donated to the Linux Foundation (June 2025), A2A is the horizontal layer: agent-to-agent collaboration across vendors and frameworks. Its signature abstraction is the Agent Card published at /.well-known/agent-card.json, plus a stateful Task lifecycle and modality-agnostic Messages and Artifacts, carried over JSON-RPC/gRPC/REST with SSE streaming. It surpassed 150 supporting organizations within its first year.

222.2.3 2.3 AP2, Agent Payments Protocol (recap)

Created by Google (September 2025), AP2 is the commerce layer, implemented as an extension over A2A. Its core abstraction is the Mandate, Intent, Cart, and Payment mandates expressed as signed Verifiable Credentials, and it is payment-method-agnostic, with a companion x402 extension (Coinbase, Ethereum Foundation, MetaMask) for stablecoin rails.

222.3 3. The Broader Field

Beyond the three core protocols, several other efforts shaped the landscape. Some merged into the winners; some occupy adjacent niches; some remain experimental. Treating them honestly, including which ones lost, is what makes the consolidation story legible.

222.3.1 3.1 ACP (IBM / BeeAI), Merged into A2A

IBM Research launched the Agent Communication Protocol (ACP) in March 2025 to power its open-source BeeAI platform, using REST and multipart HTTP messaging rather than A2A’s JSON-RPC. It was donated to the Linux Foundation shortly after. The decisive event came on September 1, 2025: the ACP team announced it was merging into A2A under the Linux Foundation to build a single unified standard, and BeeAI moved onto A2A. In IBM’s framing, “by bringing the assets and expertise behind ACP into A2A, we can build a single, more powerful standard.” ACP is therefore no longer an independent competitor; it is the clearest single data point for the convergence thesis, a direct rival folding into the standard rather than fragmenting the market.

222.3.2 3.2 AGNTCY / “Internet of Agents” (Cisco-led)

Open-sourced by Cisco’s Outshift incubator in March 2025 with LangChain and Galileo as collaborators, and welcomed as a Linux Foundation project in late July 2025, AGNTCY is broader than a single wire protocol. It provides infrastructure for multi-agent systems: the Open Agent Schema Framework (OASF) for describing and discovering agents, an Agent Directory, cryptographically verifiable Agent Identity, SLIM messaging, and observability tooling. It is positioned as complementary plumbing beneath agent-to-agent coordination rather than a competitor to A2A. One naming hazard deserves explicit warning: AGNTCY’s Agent Connect Protocol is also abbreviated ACP, colliding with IBM’s now-merged Agent Communication Protocol. They are entirely different things; secondary literature frequently conflates them.

222.3.3 3.3 Vendor Stances: Microsoft and OpenAI

The two largest non-Google players adopted the open stack rather than launching rivals, itself a strong consolidation signal.

Microsoft joined the MCP steering committee at Build 2025, shipped MCP support in VS Code (GA July 2025), and was an A2A founding supporter. It also introduced NLWeb, an open project that turns any website into a natural-language interface for agents, positioned as “HTML for the agentic web,” a content-access layer beneath agent coordination.
OpenAI adopted MCP in March 2025 across its Agents SDK, Responses API, and ChatGPT desktop app, and joined the steering committee. In December 2025 it co-founded the Agentic AI Foundation, contributing AGENTS.md, a simple repository-level instruction file for coding agents.

222.3.4 3.4 The Experimental Tier

A long tail of efforts remains real but low-adoption, and should be understood as the fringe rather than as peers of MCP/A2A:

Eclipse LMOS (Language Model Operating System), an Eclipse Foundation project for an open, “sovereign” Internet of Agents, describing capabilities in JSON-LD and remaining transport-agnostic via the W3C Web of Things; it added an Agent Definition Language in 2025. European, open-governance flavored, with modest adoption.
Coral Protocol, decentralized, Web3-flavored collaboration: threaded messaging through a Coral Server, agents bound to self-sovereign DIDs, and on-chain escrow micropayments via a token. Notably, it uses MCP as its communication substrate; its differentiator is blockchain-native trust and payments.
agent.json / Agentic Profile, lightweight, decentralized-identity-oriented descriptors for capability advertisement; niche and fluid.

222.3.5 3.5 Comparison

Protocol	Creator (date)	Layer / problem	Transport	Core abstraction	Governance (early 2026)	Maturity
MCP	Anthropic (Nov 2024)	Agent ↔︎ tools/data	JSON-RPC over stdio + Streamable HTTP	Tools, resources, prompts	Agentic AI Foundation / LF	Very high
A2A	Google (Apr 2025)	Agent ↔︎ agent	JSON-RPC / HTTP+SSE; gRPC, REST	Agent Card, Task, Artifact	Linux Foundation	High
AP2	Google (Sep 2025)	Agent payments	Extension over A2A; signed VCs	Mandates (Intent/Cart/Payment)	Open project; FIDO-aligned	Growing
ACP (IBM/BeeAI)	IBM (Mar 2025)	Agent ↔︎ agent	REST / multipart HTTP	REST agent messaging	Merged into A2A (Sep 2025)	Deprecated
AGNTCY	Cisco (Mar 2025)	Multi-agent infrastructure	SLIM; multiple	OASF, Agent Directory, identity	Linux Foundation	Medium-high
NLWeb	Microsoft (May 2025)	Website ↔︎ agent	Builds on MCP	NL interface over site content	Microsoft open project	Emerging
LMOS	Eclipse	Open “Internet of Agents”	Transport-agnostic (W3C WoT)	JSON-LD capability docs	Eclipse Foundation	Modest
Coral	Coral Protocol	Decentralized collab + payments	Coral Server; uses MCP	Threads, DIDs, on-chain escrow	Decentralized / Web3	Niche

222.4 4. The Consolidation Narrative

The defining dynamic of 2025 was convergence, and the Linux Foundation was its center of gravity. Four moves trace the arc:

A2A → Linux Foundation (June 2025) gave agent-to-agent communication a vendor-neutral home, letting competitors adopt it without ceding control to Google.
AGNTCY → Linux Foundation (July 2025) brought Cisco’s infrastructure stack under the same roof.
IBM’s ACP merged into A2A (September 2025), a direct competitor choosing consolidation over fragmentation, the single strongest signal of the “one standard” thesis.
The Agentic AI Foundation (AAIF) launched December 9, 2025, co-founded by Anthropic, Block, and OpenAI with backing from Google, Microsoft, AWS, Cloudflare, and Bloomberg, anchored by MCP (alongside Block’s goose and OpenAI’s AGENTS.md). This placed the field’s most important protocol under neutral governance with fierce commercial rivals sitting on the same board.

The repeated industry framing, stated by Google, Microsoft, IBM, and Anthropic alike, is “complementary, not competing”: MCP for tools, A2A for agents, AP2 for payments, each a distinct layer. The historical analogy the AAIF announcement makes explicit is to Kubernetes and PyTorch: foundational technologies placed under neutral foundation stewardship that preserved their existing maintainer communities while removing single-vendor control as an adoption barrier. For a graduate reader, that analogy is the right lens: the agent protocols are following the same institutional path that container orchestration and deep-learning frameworks took a decade earlier, and for the same reason, infrastructure on which an entire industry depends cannot be owned by one of its competitors.

222.5 5. Reading the Landscape Going Forward

Because this field is moving quickly, the most useful skill is not a snapshot of which protocol is “ahead” but a method for placing any new entrant. Three questions suffice:

Which layer does it occupy? Tools, agent-to-agent, commerce, content access, or cross-cutting infrastructure. If it duplicates a layer that already has a Linux Foundation, governed winner, it faces a steep adoption climb.
What is its governance trajectory? A single-vendor protocol with no neutral-foundation path is a strategic risk for adopters regardless of technical merit; the protocols that won did so substantially by ceding control.
Does it compose or compete? The stack rewards protocols that explicitly layer on others (AP2 on A2A, NLWeb on MCP, Coral on MCP) and penalizes those that try to own multiple layers at once.

Several uncertainties are worth carrying forward honestly. AP2’s governance home is the least settled of the major three. The AGNTCY/A2A boundary, infrastructure versus wire protocol, is still being negotiated, as both live under the same foundation. The “ACP” acronym collision is a persistent source of confusion. And adoption figures cited throughout this part originate largely from vendor press releases rather than independent measurement, and should be read with that provenance in mind.

222.6 6. Conclusion

The agent-interoperability landscape resolved, over the course of 2025, from apparent chaos into a coherent layered stack: MCP for tools, A2A for agents, AP2 for commerce, with content-access and infrastructure standards arrayed around them, and the Linux Foundation serving as neutral steward for the core. The protocols that thrived embraced composition and ceded governance; the ones that competed head-on either merged into the winners or remained niche. That pattern, standardize the substrate, layer specialized protocols above it, and place the substrate under neutral governance, is the durable lesson, and it is very likely the template the next wave of agentic standards will follow.

222.7 References

Linux Foundation. “Linux Foundation Announces the Formation of the Agentic AI Foundation.” December 9, 2025. https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation
Model Context Protocol Blog. “MCP joins the Agentic AI Foundation.” December 9, 2025. https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/
Model Context Protocol Blog. “Governance for MCP.” July 31, 2025. https://blog.modelcontextprotocol.io/posts/2025-07-31-governance-for-mcp/
Linux Foundation. “Linux Foundation Launches the Agent2Agent Protocol Project.” June 23, 2025. https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents
LF AI & Data. “ACP joins forces with A2A under the Linux Foundation.” August 29, 2025. https://lfaidata.foundation/communityblog/2025/08/29/acp-joins-forces-with-a2a-under-the-linux-foundations-lf-ai-data/
Linux Foundation. “Linux Foundation Welcomes the AGNTCY Project.” July 2025. https://www.linuxfoundation.org/press/linux-foundation-welcomes-the-agntcy-project-to-standardize-open-multi-agent-system-infrastructure-and-break-down-ai-agent-silos
Microsoft. “Microsoft Build 2025: The age of AI agents and building the open agentic web.” May 19, 2025. https://blogs.microsoft.com/blog/2025/05/19/microsoft-build-2025-the-age-of-ai-agents-and-building-the-open-agentic-web/
Google Cloud. “Announcing the Agent Payments Protocol (AP2).” September 16, 2025. https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol
Search Engine Journal. “MCP, A2A, NLWeb, and AGENTS.md: The Standards Powering the Agentic Web.” https://www.searchenginejournal.com/mcp-a2a-nlweb-and-agents-md-the-standards-powering-the-agentic-web/570092/

# The Agent Interoperability Landscape: Standards, Consolidation, and the Agent Stack ## 1. Introduction The three preceding chapters examined MCP, A2A, and AP2 individually. This chapter steps back to survey the entire field of agent-interoperability standards as it stood in early 2026, and, more importantly, to explain the *shape* the field took. The story of 2025 is not a proliferation of competing protocols but a rapid **consolidation** of them: a movement from a sprawl of overlapping specifications toward a layered, "complementary-not-competing" stack, with the **Linux Foundation** emerging as the dominant neutral steward. Understanding that consolidation is more durable knowledge than memorizing any single protocol, because it tells you how to reason about the next standard that appears. We proceed in three passes: a brief recap of the major protocols organized by the layer each occupies; a comparison of the broader field including the standards that lost, merged, or remain niche; and an analysis of the consolidation dynamic itself, culminating in the December 2025 formation of the Agentic AI Foundation. ## 2. The Agent Stack The mental model that crystallized over 2025 is a stack of layers, each protocol owning a distinct concern: ```{mermaid} flowchart TD L1["Content access: NLWeb, websites and agents"] L2["Commerce: AP2 plus x402, agents move money"] L3["Agent to agent: A2A, peers discover and delegate"] L4["Agent to tools: MCP, tools, resources, data"] L5["Multi-agent infra: AGNTCY/OASF, directory, identity, obs"] L1 --> L2 --> L3 --> L4 --> L5 ``` A useful one-line summary: **MCP connects an agent downward to tools; A2A connects agents sideways to peers; AP2 sits above to move money; and infrastructure projects such as AGNTCY and content layers such as NLWeb provide the directory, identity, and content-access scaffolding around them.** These are not rivals fighting for the same slot, they compose. ### 2.1 MCP, Model Context Protocol (recap) Created by Anthropic and open-sourced in November 2024, MCP is the *vertical* layer: a single agent's connection to external tools, data, and resources, often described as "the USB-C port for AI." It uses JSON-RPC 2.0 over stdio (local) and Streamable HTTP (remote, which superseded the earlier HTTP+SSE transport), and exposes three primitives, **tools, resources, and prompts**, from an MCP *server* to an MCP *client*. Anthropic introduced a formal governance model in July 2025 (Specification Enhancement Proposals and a maintainer steering group), Microsoft and OpenAI joined the steering committee in 2025, and on December 9, 2025, MCP became a founding project of the Agentic AI Foundation. It is the most mature and widely adopted of all these standards, with well over ten thousand published servers and support across every major assistant. ### 2.2 A2A, Agent2Agent (recap) Created by Google (April 2025) and donated to the Linux Foundation (June 2025), A2A is the *horizontal* layer: agent-to-agent collaboration across vendors and frameworks. Its signature abstraction is the **Agent Card** published at `/.well-known/agent-card.json`, plus a stateful **Task** lifecycle and modality-agnostic **Messages** and **Artifacts**, carried over JSON-RPC/gRPC/REST with SSE streaming. It surpassed 150 supporting organizations within its first year. ### 2.3 AP2, Agent Payments Protocol (recap) Created by Google (September 2025), AP2 is the *commerce* layer, implemented as an extension over A2A. Its core abstraction is the **Mandate**, Intent, Cart, and Payment mandates expressed as signed Verifiable Credentials, and it is payment-method-agnostic, with a companion **x402** extension (Coinbase, Ethereum Foundation, MetaMask) for stablecoin rails. ## 3. The Broader Field Beyond the three core protocols, several other efforts shaped the landscape. Some merged into the winners; some occupy adjacent niches; some remain experimental. Treating them honestly, including which ones *lost*, is what makes the consolidation story legible. ### 3.1 ACP (IBM / BeeAI), Merged into A2A IBM Research launched the **Agent Communication Protocol (ACP)** in March 2025 to power its open-source BeeAI platform, using REST and multipart HTTP messaging rather than A2A's JSON-RPC. It was donated to the Linux Foundation shortly after. The decisive event came on **September 1, 2025**: the ACP team announced it was **merging into A2A** under the Linux Foundation to build a single unified standard, and BeeAI moved onto A2A. In IBM's framing, "by bringing the assets and expertise behind ACP into A2A, we can build a single, more powerful standard." ACP is therefore no longer an independent competitor; it is the clearest single data point for the convergence thesis, a direct rival folding *into* the standard rather than fragmenting the market. ### 3.2 AGNTCY / "Internet of Agents" (Cisco-led) Open-sourced by Cisco's Outshift incubator in March 2025 with LangChain and Galileo as collaborators, and welcomed as a Linux Foundation project in late July 2025, **AGNTCY** is broader than a single wire protocol. It provides *infrastructure* for multi-agent systems: the **Open Agent Schema Framework (OASF)** for describing and discovering agents, an **Agent Directory**, cryptographically verifiable **Agent Identity**, **SLIM** messaging, and observability tooling. It is positioned as complementary plumbing beneath agent-to-agent coordination rather than a competitor to A2A. One naming hazard deserves explicit warning: AGNTCY's **Agent Connect Protocol** is also abbreviated **ACP**, colliding with IBM's now-merged Agent Communication Protocol. They are entirely different things; secondary literature frequently conflates them. ### 3.3 Vendor Stances: Microsoft and OpenAI The two largest non-Google players adopted the open stack rather than launching rivals, itself a strong consolidation signal. - **Microsoft** joined the MCP steering committee at Build 2025, shipped MCP support in VS Code (GA July 2025), and was an A2A founding supporter. It also introduced **NLWeb**, an open project that turns any website into a natural-language interface for agents, positioned as "HTML for the agentic web," a content-access layer beneath agent coordination. - **OpenAI** adopted **MCP in March 2025** across its Agents SDK, Responses API, and ChatGPT desktop app, and joined the steering committee. In December 2025 it co-founded the Agentic AI Foundation, contributing **AGENTS.md**, a simple repository-level instruction file for coding agents. ### 3.4 The Experimental Tier A long tail of efforts remains real but low-adoption, and should be understood as the fringe rather than as peers of MCP/A2A: - **Eclipse LMOS** (Language Model Operating System), an Eclipse Foundation project for an open, "sovereign" Internet of Agents, describing capabilities in JSON-LD and remaining transport-agnostic via the W3C Web of Things; it added an Agent Definition Language in 2025. European, open-governance flavored, with modest adoption. - **Coral Protocol**, decentralized, Web3-flavored collaboration: threaded messaging through a Coral Server, agents bound to self-sovereign DIDs, and on-chain escrow micropayments via a token. Notably, it *uses MCP* as its communication substrate; its differentiator is blockchain-native trust and payments. - **agent.json / Agentic Profile**, lightweight, decentralized-identity-oriented descriptors for capability advertisement; niche and fluid. ### 3.5 Comparison | Protocol | Creator (date) | Layer / problem | Transport | Core abstraction | Governance (early 2026) | Maturity | |---|---|---|---|---|---|---| | **MCP** | Anthropic (Nov 2024) | Agent ↔ tools/data | JSON-RPC over stdio + Streamable HTTP | Tools, resources, prompts | Agentic AI Foundation / LF | Very high | | **A2A** | Google (Apr 2025) | Agent ↔ agent | JSON-RPC / HTTP+SSE; gRPC, REST | Agent Card, Task, Artifact | Linux Foundation | High | | **AP2** | Google (Sep 2025) | Agent payments | Extension over A2A; signed VCs | Mandates (Intent/Cart/Payment) | Open project; FIDO-aligned | Growing | | **ACP** (IBM/BeeAI) | IBM (Mar 2025) | Agent ↔ agent | REST / multipart HTTP | REST agent messaging | **Merged into A2A** (Sep 2025) | Deprecated | | **AGNTCY** | Cisco (Mar 2025) | Multi-agent infrastructure | SLIM; multiple | OASF, Agent Directory, identity | Linux Foundation | Medium-high | | **NLWeb** | Microsoft (May 2025) | Website ↔ agent | Builds on MCP | NL interface over site content | Microsoft open project | Emerging | | **LMOS** | Eclipse | Open "Internet of Agents" | Transport-agnostic (W3C WoT) | JSON-LD capability docs | Eclipse Foundation | Modest | | **Coral** | Coral Protocol | Decentralized collab + payments | Coral Server; uses MCP | Threads, DIDs, on-chain escrow | Decentralized / Web3 | Niche | ## 4. The Consolidation Narrative The defining dynamic of 2025 was convergence, and the Linux Foundation was its center of gravity. Four moves trace the arc: 1. **A2A → Linux Foundation (June 2025)** gave agent-to-agent communication a vendor-neutral home, letting competitors adopt it without ceding control to Google. 2. **AGNTCY → Linux Foundation (July 2025)** brought Cisco's infrastructure stack under the same roof. 3. **IBM's ACP merged into A2A (September 2025)**, a direct competitor choosing consolidation over fragmentation, the single strongest signal of the "one standard" thesis. 4. **The Agentic AI Foundation (AAIF) launched December 9, 2025**, co-founded by Anthropic, Block, and OpenAI with backing from Google, Microsoft, AWS, Cloudflare, and Bloomberg, anchored by MCP (alongside Block's *goose* and OpenAI's *AGENTS.md*). This placed the field's most important protocol under neutral governance with fierce commercial rivals sitting on the same board. The repeated industry framing, stated by Google, Microsoft, IBM, and Anthropic alike, is **"complementary, not competing"**: MCP for tools, A2A for agents, AP2 for payments, each a distinct layer. The historical analogy the AAIF announcement makes explicit is to **Kubernetes and PyTorch**: foundational technologies placed under neutral foundation stewardship that preserved their existing maintainer communities while removing single-vendor control as an adoption barrier. For a graduate reader, that analogy is the right lens: the agent protocols are following the same institutional path that container orchestration and deep-learning frameworks took a decade earlier, and for the same reason, infrastructure on which an entire industry depends cannot be owned by one of its competitors. ## 5. Reading the Landscape Going Forward Because this field is moving quickly, the most useful skill is not a snapshot of which protocol is "ahead" but a method for placing any new entrant. Three questions suffice: 1. **Which layer does it occupy?** Tools, agent-to-agent, commerce, content access, or cross-cutting infrastructure. If it duplicates a layer that already has a Linux Foundation, governed winner, it faces a steep adoption climb. 2. **What is its governance trajectory?** A single-vendor protocol with no neutral-foundation path is a strategic risk for adopters regardless of technical merit; the protocols that won did so substantially by ceding control. 3. **Does it compose or compete?** The stack rewards protocols that explicitly layer on others (AP2 on A2A, NLWeb on MCP, Coral on MCP) and penalizes those that try to own multiple layers at once. Several uncertainties are worth carrying forward honestly. AP2's governance home is the least settled of the major three. The AGNTCY/A2A boundary, infrastructure versus wire protocol, is still being negotiated, as both live under the same foundation. The "ACP" acronym collision is a persistent source of confusion. And adoption figures cited throughout this part originate largely from vendor press releases rather than independent measurement, and should be read with that provenance in mind. ## 6. Conclusion The agent-interoperability landscape resolved, over the course of 2025, from apparent chaos into a coherent layered stack: MCP for tools, A2A for agents, AP2 for commerce, with content-access and infrastructure standards arrayed around them, and the Linux Foundation serving as neutral steward for the core. The protocols that thrived embraced composition and ceded governance; the ones that competed head-on either merged into the winners or remained niche. That pattern, standardize the substrate, layer specialized protocols above it, and place the substrate under neutral governance, is the durable lesson, and it is very likely the template the next wave of agentic standards will follow. ## References 1. Linux Foundation. "Linux Foundation Announces the Formation of the Agentic AI Foundation." December 9, 2025. https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation 2. Model Context Protocol Blog. "MCP joins the Agentic AI Foundation." December 9, 2025. https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/ 3. Model Context Protocol Blog. "Governance for MCP." July 31, 2025. https://blog.modelcontextprotocol.io/posts/2025-07-31-governance-for-mcp/ 4. Linux Foundation. "Linux Foundation Launches the Agent2Agent Protocol Project." June 23, 2025. https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents 5. LF AI & Data. "ACP joins forces with A2A under the Linux Foundation." August 29, 2025. https://lfaidata.foundation/communityblog/2025/08/29/acp-joins-forces-with-a2a-under-the-linux-foundations-lf-ai-data/ 6. Linux Foundation. "Linux Foundation Welcomes the AGNTCY Project." July 2025. https://www.linuxfoundation.org/press/linux-foundation-welcomes-the-agntcy-project-to-standardize-open-multi-agent-system-infrastructure-and-break-down-ai-agent-silos 7. Microsoft. "Microsoft Build 2025: The age of AI agents and building the open agentic web." May 19, 2025. https://blogs.microsoft.com/blog/2025/05/19/microsoft-build-2025-the-age-of-ai-agents-and-building-the-open-agentic-web/ 8. Google Cloud. "Announcing the Agent Payments Protocol (AP2)." September 16, 2025. https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol 9. Search Engine Journal. "MCP, A2A, NLWeb, and AGENTS.md: The Standards Powering the Agentic Web." https://www.searchenginejournal.com/mcp-a2a-nlweb-and-agents-md-the-standards-powering-the-agentic-web/570092/