---
title: "NANDA (Networked Agents And Decentralized AI)"
source: Panaversity Learn Agentic AI
source_url: https://github.com/panaversity/learn-agentic-ai
licence: Apache-2.0
domain: agentic-ai
subdomain: panaversity-agentic
date_added: 2026-04-25
---

# NANDA (Networked Agents And Decentralized AI)

[Make A Decentralized Internet With AI: NANDA Is Coming](https://www.forbes.com/sites/johnwerner/2025/05/13/make-a-decentralized-internet-with-ai-nanda-is-coming/)

[They’re Making TCP/IP For AI, And It’s Called NANDA](https://www.forbes.com/sites/johnwerner/2025/04/29/theyre-making-tcpip-for-ai-and-its-called-nanda/)

[Official Website](https://nanda.media.mit.edu/)

[Beyond DNS: Unlocking the Internet of AI Agents via the NANDA Index and Verified AgentFacts](https://arxiv.org/abs/2507.14263)

[A Survey of AI Agent Registry Solutions](https://arxiv.org/html/2508.03095v1)

“Project NANDA” refers to **Networked Agents And Decentralized AI**—an ambitious initiative developed at MIT that’s essentially building the “Internet for AI agents.” 

As we move from single chatbots to **ecosystems of AI agents**, we need common ways for agents to *find*, *trust*, and *talk to* each other across companies and clouds—otherwise every integration is a bespoke blind date with awkward small talk. **Project NANDA** (MIT) proposes the “Internet of AI Agents”: a discovery-and-trust fabric so agents can be located, identified, verified, and routed like services on the web. Think “DNS + PKI + smart routing,” but for agents that collaborate and transact, not just serve static pages—yes, it’s DNS with espresso.

A key technical piece is the **NANDA Index** backed by **Verified AgentFacts**—cryptographically signed metadata about an agent’s identity, capabilities, endpoints, and policies. The Index gives **fast resolution**, **key rotation**, **privacy-preserving queries**, and **schema-validated capability assertions** (say that three times fast). It’s “Beyond DNS” because it resolves to verifiable, dynamic facts rather than just IPs. 

Here’s a breakdown of what that entails and why it matters:

---

## What Is Project NANDA?

**NANDA** is an open, decentralized infrastructure aiming to enable a vast ecosystem of autonomous AI agents to discover, verify, communicate, and collaborate across diverse platforms and protocols.

* It builds upon protocols like Anthropic’s MCP (Model Context Protocol) and Google’s A2A (Agent-to-Agent), orchestrating them within a unified, decentralized network.([nanda.media.mit.edu][1], [numorpho.org][2], [LinkedIn][3])
* Project NANDA provides the infrastructure necessary for an **“Internet of AI Agents”**, where agents—from individuals, businesses, or institutions—can operate, transact, and evolve across a federated landscape.([LinkedIn][3], [Forbes][4], [numorpho.org][2])

---

## Why It Matters

Think of NANDA as building the **TCP/IP or DNS layer for AI agents**—creating the backbone they need to interact securely, seamlessly, and scalably.

* It functions as a **universal adapter**: NANDA allows agents across different frameworks to understand and communicate with each other without needing shared protocol languages.([LinkedIn][5], [Forbes][4])
* It offers a **decentralized registry system** (akin to domain resolution), enabling agents to find one another across a federated network.([Forbes][4], [LinkedIn][3], [Medium][6], [Wikipedia][7])
* NANDA includes **secure identity, trust, and verification layers**, ensuring interactions are auditable, trustworthy, and resistant to impersonation.([Medium][6], [arXiv][8], [LinkedIn][3])

---

## Core Components & Innovations

### 1. **Agent Discovery & Registry**

Agents can locate and communicate with other agents through a federated registry—think of it as NANDA’s version of DNS for agent identities.([nanda.media.mit.edu][1], [numorpho.org][2], [Medium][6], [arXiv][9])

### 2. **Identity, Trust & Accountability**

Agents have cryptographic identities, signing every interaction to ensure accountability and establish trust.([Medium][6], [numorpho.org][2], [arXiv][8])

### 3. **Protocol Interoperability**

NANDA doesn’t replace existing protocols—it wraps around them, enabling cross-protocol interoperability (MCP, A2A, HTTPS, NLWeb) through a modular “quilt” structure.([nanda.media.mit.edu][1], [numorpho.org][2], [LinkedIn][3], [Medium][6], [Forbes][4], [velocityascent.com][10])

### 4. **Economic & Incentive Systems**

The architecture includes vision for economic layers—agents can be rewarded for useful actions via tokens, credits, or traceable contributions.([Medium][6], [numorpho.org][2], [velocityascent.com][10])

### 5. **Adaptive Resolver**

NANDA is extending its registry with dynamic resolution: agents can choose communication endpoints based on regional load, context, or security, the way an intelligent routing layer might.([arXiv][11])

### 6. **Scoping & Architecture Phases**

Project NANDA is rolling out in phases:

* **Phase 1: Agentic Web Foundations** (agent discovery, communication, security)
* **Phase 2: Agentic Commerce** (economic and marketplace features)
* **Phase 3: Society of Agents** (collaborative networks and emergent behaviors)([LinkedIn][12])

### 7. **Enterprise & Research Applications**

A recent paper outlines NANDA’s framework for secure, interoperable multi-agent systems that support discovery, credential verification, and cross-protocol security in enterprise environments.([arXiv][8])
Additional research explores registry models, metadata standards like AgentFacts, and trust mechanisms across protocols.([arXiv][9])

---

## Summary Table

| Feature                 | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| **Registry**            | Federated agent discovery (like DNS)                   |
| **Identity & Trust**    | Cryptographically secure agent identities              |
| **Protocol Bridge**     | Interoperability across MCP, A2A, HTTPS, NLWeb         |
| **Economic Incentives** | Framework for rewards, tokens, and proof-of-work       |
| **Dynamic Routing**     | Context-aware endpoint resolution                      |
| **Roadmap**             | Phased build: infrastructure → economy → collaboration |

---

## In a Nutshell

Project NANDA is laying the foundation for a decentralized ecosystem where AI agents can:

* Autonomously **discover** and **authenticate** each other,
* Seamlessly **communicate** regardless of platform,
* **Transact and cooperate**, all under transparent governance mechanisms.


[1]: https://nanda.media.mit.edu/index.html?utm_source=chatgpt.com "NANDA - The Internet of AI Agents"
[2]: https://numorpho.org/whitepapers/mantra-m5-thesis-brief-71/?utm_source=chatgpt.com "Mantra M5 Thesis Brief 71 – Platform Evolution 1: Tenets – EVERYTHING CONNECTED – Numorpho's Book of Business"
[3]: https://www.linkedin.com/pulse/project-nanda-internet-ai-agents-mason-nguyen-uyy7c?utm_source=chatgpt.com "Project NANDA: The Internet of AI Agents"
[4]: https://www.forbes.com/sites/johnwerner/2025/04/29/theyre-making-tcpip-for-ai-and-its-called-nanda/?utm_source=chatgpt.com "They’re Making TCP/IP For AI, And It’s Called NANDA"
[5]: https://www.linkedin.com/pulse/revolution-you-havent-heard-why-project-nanda-could-change-reganti-tidmc?utm_source=chatgpt.com "The Revolution You Haven't Heard About: Why Project NANDA Could Change Everything"
[6]: https://rahulshah19.medium.com/nanda-the-internet-stack-for-ai-agents-70bc8d706323?utm_source=chatgpt.com "NANDA: The Internet Stack for AI Agents | by Rahulshah | Medium"
[7]: https://en.wikipedia.org/wiki/Santanu_Bhattacharya_%28data_scientist%29?utm_source=chatgpt.com "Santanu Bhattacharya (data scientist)"
[8]: https://arxiv.org/abs/2508.03101?utm_source=chatgpt.com "Using the NANDA Index Architecture in Practice: An Enterprise Perspective"
[9]: https://arxiv.org/abs/2508.03095?utm_source=chatgpt.com "A Survey of AI Agent Registry Solutions"
[10]: https://velocityascent.com/nanda-networked-agents-and-decentralized-ai/?utm_source=chatgpt.com "NANDA: Networked Agents And Decentralized AI"
[11]: https://arxiv.org/abs/2508.03113?utm_source=chatgpt.com "NANDA Adaptive Resolver: Architecture for Dynamic Resolution of AI Agent Names"
[12]: https://www.linkedin.com/posts/projectnanda_projectnanda-agenticweb-ai-activity-7357456121487388672-qzio?utm_source=chatgpt.com "An electrifying gathering of minds in SF! | Project NANDA: Architecting the Internet of AI Agents"


## How NANDA Relates to MCP/A2A

Great question. Project **NANDA** doesn’t compete with **MCP (Model Context Protocol)** or **A2A (Agent-to-Agent protocol from Google)** — instead it’s designed as the **interoperability and discovery layer that stitches them together**.

Here’s how the pieces fit:

---

## 🔗 NANDA vs MCP vs A2A

| Layer                            | Purpose                                                                                                           | Where NANDA Fits                                                                                                                                                                            |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **MCP (Model Context Protocol)** | Standardizes how LLMs/agents talk to external tools, data sources, and extensions. It’s “agent ↔ tools.”          | NANDA treats MCP agents as *nodes* on its network. It provides a registry, identity, and trust system so MCP agents can be found, verified, and securely connected across domains.          |
| **A2A (Agent-to-Agent)**         | Google’s emerging protocol for agent ↔ agent conversations (structured messages, negotiation, and orchestration). | NANDA allows A2A agents to interoperate with MCP agents (and others) by acting as a **bridge layer**. It doesn’t replace A2A—it lets A2A traffic flow securely across different ecosystems. |
| **NANDA**                        | Network infrastructure: discovery, identity, trust, cross-protocol routing (like TCP/IP + DNS for agents).        | Provides a universal addressing system and registry so MCP and A2A agents can *find each other*, authenticate, and talk—regardless of protocol differences.                                 |

---

## 🌍 How They Work Together

1. **Discovery & Registry**

   * NANDA provides a DNS-like service so that MCP agents, A2A agents, or any other protocol participants can be discovered with metadata (capabilities, trust level, ownership).
   * Example: An A2A scheduling agent can query NANDA to find an MCP-based calendar agent.

2. **Identity & Trust**

   * Every agent has a cryptographic identity in NANDA.
   * Whether the agent speaks MCP or A2A, NANDA signs and verifies messages, preventing impersonation.

3. **Protocol Interoperability**

   * MCP focuses on “agent ↔ tool,” while A2A focuses on “agent ↔ agent.”
   * NANDA acts like a **router/adapter** so these protocols can coexist and interoperate instead of fragmenting.

4. **Dynamic Resolution**

   * NANDA can route conversations intelligently: e.g., a request from an A2A agent may be routed through an MCP extension if that’s the only available capability.

---

## 📌 Analogy

* **MCP** = USB protocol (plug tools into agents).
* **A2A** = Bluetooth protocol (agents talking directly).
* **NANDA** = The Internet stack (DNS + TCP/IP) that ensures both USB and Bluetooth devices can be *found, identified, and connected* across networks.

---

👉 In short: **MCP and A2A handle the *content and structure* of communication. NANDA handles the *infrastructure, discovery, and interoperability*.**

## NANDA × MCP × A2A — one-page crib sheet (the “USB-C, Bluetooth & Internet” of agents)

**TL;DR**

* **MCP** = agents ↔ tools (think *USB-C for capabilities*); **A2A** = agent ↔ agent (think *Bluetooth for negotiations*); **NANDA** = discovery, identity, trust, routing (think *DNS/PKI + roads*). If MCP and A2A are the band, NANDA is the stage, lights, and the bouncer with the guest list. ([Anthropic][1], [modelcontextprotocol.io][2], [NANDA][3])

**What NANDA is (and why you care)**

* MIT’s **Project NANDA** (“Networked Agents & Decentralized AI”) aims to build the open **Internet of AI Agents**: a federated **Index** that resolves agent IDs to **Verified AgentFacts** (identity, capabilities, endpoints, policy) with cryptographic guarantees and fast revocation—basically *DNS with superpowers and fewer SPF headaches*. ([NANDA][3], [ar5iv][4])

**How NANDA relates to MCP & A2A**

* **NANDA** is the fabric: *find → verify → route*. **MCP** standardizes tool access so agents call actions safely. **A2A** standardizes inter-agent collaboration and task lifecycles. Together they prevent protocol silos—like adapters that finally fit without duct tape. ([modelcontextprotocol.io][2], [Anthropic][5], [Google Developers Blog][6], [Linux Foundation][7])

**Core artifacts (mental models)**

* **NANDA Index & Verified AgentFacts**: signed metadata enabling discovery, least-disclosure queries, multi-endpoint routing, and sub-second key rotation—your agents get passports, not sticky notes. ([ar5iv][4])
* **MCP Tools**: schema-described actions/resources exposed by servers and invoked by clients—finally, one plug that isn’t proprietary triangle-shaped. ([Anthropic][1], [modelcontextprotocol.io][2])
* **A2A Agent Cards & Tasks**: capability ads + structured, multi-modal exchanges over web transports—basically LinkedIn + Trello for bots (minus humble-bragging). ([Google Developers Blog][6], [Google Codelabs][8])

**Reference flow (concept-only)**

1. **Discover**: Client asks NANDA for “who can `calendar.schedule`?” (no more yelling into the void).
2. **Verify & Resolve**: NANDA returns **AgentFacts** + endpoints (IDs checked, fake moustaches removed).
3. **Negotiate**: Agents coordinate via **A2A** (who does what, when, with which artifacts).
4. **Execute**: The doer calls **MCP** tools to act (sharp knives, safe kitchen). 

**Security & governance (why CISOs sleep)**

* Crypto identities, signed facts, privacy-preserving discovery; A2A now under **Linux Foundation** for neutral stewardship—open standards that age like wine, not milk. ([Linux Foundation][7], [Google Developers Blog][9])

**When to use what (quick rules)**

* Ask “*Who can I trust to do X?*” → **NANDA**; “*How to perform X on systems?*” → **MCP**; “*Which agent will do X and how do we coordinate?*” → **A2A**—like picking shoes: boots (NANDA), cleats (MCP), dance shoes (A2A). ([Anthropic][1], [Google Developers Blog][6])

**Design tips (interop without tears)**

* Use shared **capability names** (e.g., `calendar.schedule`), keep **AgentFacts** small and signed, prefer **least-disclosure** queries, and let NANDA bridge protocols—more jazz ensemble, less drum solo. ([ar5iv][4])

**Pointers to the canonical stuff**

* **NANDA**: MIT site + **NANDA Index & Verified AgentFacts** paper (“Beyond DNS”). ([NANDA][3], [ar5iv][4])
* **MCP**: official docs + current spec. ([Anthropic][1], [modelcontextprotocol.io][2])
* **A2A**: Google’s announcement + Linux Foundation project updates. (Yes, the grown-ups are in the room.) ([Google Developers Blog][6], [Linux Foundation][7])

- [The Verge](https://www.theverge.com/news/669298/microsoft-windows-ai-foundry-mcp-support?utm_source=chatgpt.com)
- [axios.com](https://www.axios.com/2025/04/17/model-context-protocol-anthropic-open-source?utm_source=chatgpt.com)
- [techradar.com](https://www.techradar.com/pro/what-is-model-context-protocol-and-why-does-it-matter-to-software-engineers?utm_source=chatgpt.com)

[1]: https://docs.anthropic.com/en/docs/mcp?utm_source=chatgpt.com "Model Context Protocol (MCP)"
[2]: https://modelcontextprotocol.io/specification/2025-06-18?utm_source=chatgpt.com "Specification"
[3]: https://nanda.mit.edu/ "NANDA - The Internet of AI Agents"
[4]: https://ar5iv.org/pdf/2507.14263 "[2507.14263] Beyond DNS: Unlocking the Internet of AI Agents via the NANDA Index and Verified AgentFacts"
[5]: https://www.anthropic.com/news/model-context-protocol?utm_source=chatgpt.com "Introducing the Model Context Protocol"
[6]: https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/?utm_source=chatgpt.com "Announcing the Agent2Agent Protocol (A2A)"
[7]: https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents?utm_source=chatgpt.com "Linux Foundation Launches the Agent2Agent Protocol ..."
[8]: https://codelabs.developers.google.com/intro-a2a-purchasing-concierge?utm_source=chatgpt.com "Getting Started with Agent-to-Agent (A2A) Protocol - Codelabs"
[9]: https://developers.googleblog.com/en/google-cloud-donates-a2a-to-linux-foundation/?utm_source=chatgpt.com "Google Cloud donates A2A to Linux Foundation"


## NANDA’s conceptual building blocks

1. **Index & Resolution**: A quilt-like, federated **Index** that resolves agent identifiers to **Verified AgentFacts**; supports rapid spin-up, revocation, and multi-endpoint routing—imagine DNS that also checks a driver’s license and routes around traffic. ([ar5iv][5])
2. **Verified AgentFacts**: Signed metadata with identity keys, capability claims, endpoints, and governance signals; **CRDT-style updates** keep facts consistent across replicas—metadata with a gym membership. ([ar5iv][5])
3. **Identity & Trust**: Cryptographic identity with **capability attestation** and least-disclosure queries; aligns with **Zero-Trust Agentic Access (ZTAA)** patterns in enterprise contexts—trust, but verify (and log), then verify again. ([arXiv][6])
4. **Cross-Protocol Interop**: One agent registry, many protocols: **MCP**, **A2A**, classic **HTTPS**, and even emerging agentic protocols—NANDA’s the switchboard, not the call script. ([arXiv][6])

## MCP: the tool & data integration theory

**MCP** defines how LLMs/agents access **tools, resources, and context** in a uniform way—servers expose **tools** with schemas; hosts/clients invoke them; models stay protocol-agnostic. It’s the ecosystem’s **tooling spine**, so we don’t keep reinventing “call this API” in 37 dialects (your future self says thanks). ([modelcontextprotocol.io][3])

## A2A: the inter-agent conversation theory

**A2A** describes **capability discovery** via **Agent Cards**, **task-centric interactions** with lifecycle and artifacts, and multi-modal **message parts**, over **HTTP/SSE/JSON-RPC**—so agents can negotiate and collaborate like teammates, not like fax machines. The project is now under **Linux Foundation governance**, which signals multi-vendor neutrality and longevity—open standards don’t age like dairy. ([Google Developers Blog][4], [Linux Foundation][7])

## The layered conceptual model (who stands where)

* **Experience layer**: UIs, human-in-the-loop, workflows (because users still exist, promise).
* **Agent layer (A2A)**: Agents discover capabilities, negotiate tasks, and exchange context—interviews, not monologues. ([Google Developers Blog][4])
* **Tooling layer (MCP)**: Agents invoke structured tools/data with stable schemas—less spaghetti, more rigatoni. ([modelcontextprotocol.io][3])
* **Fabric layer (NANDA)**: Discovery, identity, registry, trust, and cross-protocol routing—like a switchboard that also checks passports. ([MIT Media Lab][2], [ar5iv][5])

## End-to-end reference flow

1. **Discover**: A2A client needs “calendar.schedule”; it queries the **NANDA Index** for agents with matching **AgentFacts** (capability + policy). No left swipes needed. ([ar5iv][5])
2. **Verify & Resolve**: Index returns **verified facts** with cryptographic identity and endpoints; client picks a route (region, load, policy). GPS for agents, minus toll roads. ([ar5iv][5])
3. **Negotiate**: Over **A2A**, agents agree on task scope, modalities, and artifacts (the “what” and “how”). It’s a project kickoff, not a mystery novel. ([Google Developers Blog][4])
4. **Execute**: The actor agent uses **MCP tools** to perform actions (e.g., create an event) with schemas and guardrails—sharp knives in a safe kitchen. ([modelcontextprotocol.io][3])
5. **Audit & Govern**: Policies, signatures, and logs satisfy enterprise governance (ZTAA/AVC patterns), while keeping autonomy and privacy—compliance that doesn’t kill the party. ([arXiv][6])


## Open questions (worth debating over ☕)

* **Capability semantics**: How universal can capability names be across domains without becoming mush? (The “calendar.schedule” of today becomes “workflow\.compose” tomorrow.)
* **Registry federation**: How many indexes, how are they delegated, and who sets revocation norms? (DNS taught us politics hides in TXT records.) ([ar5iv][5])
* **Policy portability**: Can privacy/compliance policies travel with AgentFacts across org boundaries, or do we keep reinventing NDAs? (The legal bots want in.)
* **Adoption gravity**: Will MCP’s momentum or A2A’s enterprise focus dominate first—or will NANDA’s discovery layer make that rivalry less zero-sum? (History loves a good protocol drama.) ([modelcontextprotocol.io][3], [Google Developers Blog][4])

---

### TL;DR

* **NANDA** = the **fabric** (discovery, identity, trust, routing).
* **MCP** = the **tools/data** protocol.
* **A2A** = the **agent-to-agent** protocol.
  Used together, they enable **discoverable, trustworthy, interoperable** agent ecosystems—finally, agents that can find each other, prove who they are, and get stuff done without sticky notes.
