@changgaowei: Agree, if a messaging protocol doesn't handle identity, cross-domain is just a channel. ANP splits these two layers and reconnects them: `did:wba` answers who you are and how to verify, while the messaging Profile (1:1 / Group / E2EE / Federated) only handles how to transmit. Identity can also be used for payments, authorization, and isn't tied to a single IM...
Summary
ANP is an open-source protocol designed to provide standards for identity, naming, discovery, and secure communication for intelligent agents, separating identity from message delivery to enable cross-domain collaboration.
View Cached Full Text
Cached at: 08/18/26, 10:45 AM
Agreed, if the messaging protocol doesn’t handle identity, cross-domain communication is just a channel. ANP separates and then reconnects these two layers: did:wba answers who you are and how to verify you, while the messaging Profile (1:1, group, E2EE, federation) only handles how to deliver. The identity can also be used for payments and authorization, without being tied to any single IM system. We built an open-source protocol and a product called AWiki based on this idea (one DID, shared across phone/PC/agent, with a Handle that also includes an email).
Protocol: https://github.com/agent-network-protocol/AgentNetworkProtocol Product: —
agent-network-protocol/AgentNetworkProtocol
Source: https://github.com/agent-network-protocol/AgentNetworkProtocol
Agent Network Protocol (ANP)
ANP aims to become the HTTP of the Agentic Web era: a protocol suite for agent identity, naming, discovery, negotiation, secure messaging, and application-level collaboration.
Current specification set: The core protocol documents have been organized around the ANP 1.1 release line. The released suite covers did:wba identity, WNS handles, agent description, agent discovery, end-to-end instant messaging, and the AP2 agent payment protocol. The meta-protocol specification remains a draft and is not released yet.
ANP Messaging 1.2 draft: The mixed-version draft suite defines multi-device cryptographic endpoints under one DID while keeping P1/P2/P3/P4/P7/P8 and the P9 Mention binding on v1. Only the incompatible Direct E2EE and Group E2EE Profiles use v2. Draft presence does not imply implementation support or public capability advertisement.
Versioning note: Version: 1.1 identifies the specification/document release version. It does not change the ANP payload field protocolVersion; examples and protocol fields that use "protocolVersion": "1.0.0" remain unchanged because this release does not change protocol fields, flows, or security requirements.
Note: This project has not issued any digital currency on any platform or blockchain.
Vision and Positioning
Agent Network Protocol (ANP) is an open-source communication protocol for intelligent agents. Its goal is to define how agents connect with each other and to build an open, secure, and efficient collaboration network for billions of agents.
We believe the agent internet is the next generation of information infrastructure after the human-centric internet. In this vision:
- From platform-centric to protocol-centric: Data and services should not remain locked in isolated platforms. Agents need open protocols for direct connection.
- Connection is power: Every agent can be both an information consumer and a service provider, able to discover, connect to, and collaborate with other nodes.
- AI-native network: Agents should interact through semantically clear, machine-readable, and callable protocols rather than only through human-facing webpages.
Why We Need ANP
Current internet infrastructure is mature, but it still lacks a communication and connection layer designed for large-scale agent networks. ANP focuses on three challenges:
- 🌐 Interconnection: Enable agents from different platforms and domains to authenticate, discover, and communicate with each other.
- 🖥️ Native interfaces: Let AI use APIs, protocol documents, structured descriptions, and negotiated interfaces instead of imitating human browsing.
- 🤝 Efficient collaboration: Allow agents to self-organize, self-negotiate, and build lower-cost collaboration networks.
Protocol Architecture
ANP is built on existing Internet infrastructure and organizes the released protocol capabilities into two core protocol layers plus domain-specific application protocols:
- 🌐 Open Internet Infrastructure: ANP reuses HTTP, CA, DNS, CDN, Search, and TLS instead of rebuilding a new network stack.
- 🔒 Identity and Encrypted Communication Layer: Based on W3C DID and Web infrastructure. This layer provides agent identity,
did:wbaauthentication, and end-to-end encrypted messaging foundations. - 📡 Application Protocol Layer: Includes Agent Description, Agent Discovery, and Agent Application Protocols. Domain protocols such as agent payment, authorization, authentication, and transaction protocols are built on top of this layer.
- 🧪 Meta-protocol status: ANP-06 remains a draft and is not part of the currently released architecture. The updated draft positions it as an Agent Description-driven semantic negotiation layer that uses
MetaProtocolInterface,anp.get_capabilities, andanp.negotiateto select the subsequent interface, Profile, security profile, and schema.
Protocol Specification Index
| Area | Document | Status | What it defines |
|---|---|---|---|
| Overview | ANP Technical White Paper | White paper | Vision, design principles, and the three-layer architecture |
| Identity | ANP-03: did:wba Method Specification | Released v1.1 | Web-based DID method, cross-platform authentication, e1_ Ed25519 binding, k1_ compatibility extension |
| Naming | ANP-04: ANP-DID:WBA Name Space Specification | Released v1.1 | WNS handles such as alice.example.com, Handle-to-DID resolution, DID rotation support |
| Meta-protocol | ANP-06: Agent Communication Meta-Protocol | Draft / not released | Optional semantic meta-protocol negotiation, MetaProtocolInterface declaration, anp.negotiate, and interface / Profile / security profile / schema selection |
| Description | ANP-07: Agent Description Protocol | Released v1.1 | Agent Description documents, interface descriptions, and capability publication |
| Discovery | ANP-08: Agent Discovery Protocol | Released v1.1 | Active .well-known discovery and passive registration with search agents |
| Messaging | ANP-09: End-to-End Instant Messaging Overview | Released v1.1 + vNext Draft | Profile index for direct messaging, group messaging, E2EE, attachments, federation, mentions, and the separately versioned multi-device draft |
| Payments | ANP-10: Agent Payment Protocol (AP2) | Released v1.1 (EN); CN draft available | Agent-to-agent payments, mandates, receipts, DID-based signatures, and payment flows |
Instant Messaging Profiles
The released ANP 1.1 end-to-end instant messaging suite is split into focused profiles:
- P1 Core Binding: JSON-RPC 2.0 binding, request/response/error conventions.
- P2 Identity and Discovery: DID-based service discovery and endpoint capability discovery.
- P3 Direct Messaging Base Semantics: Direct message sending and receipts.
- P4 Group Messaging Base Semantics: Group lifecycle, membership, and group message semantics.
- P5 Direct End-to-End Encryption: E2EE overlay for direct messaging.
- P6 Group End-to-End Encryption: E2EE overlay for group messaging.
- P7 Attachments and Object Transfer: Manifests, object services, and large-object transfer.
- P8 Federation and Cross-Domain: Cross-domain routing, relaying, and result witnessing.
- P9 Message Mentions Extension: Group-message mention payloads and selector semantics.
The ANP Messaging 1.2 draft index and its Chinese mirror define a legal mixed-version capability set: Base, Attachment, and Federation remain v1, while Direct E2EE and Group E2EE use v2. Ordinary Direct, Group, Mention, and Attachment operations stay addressed only by business DID or Group DID; their device fan-out remains local to the receiving domain. device_id appears only where an E2EE v2 Profile requires a cryptographic endpoint, including independent Direct sessions and multiple MLS leaves, and P8 v1 preserves device selectors only for such enclosing Profiles. Implementations MUST NOT reinterpret E2EE v1 state as v2 or silently downgrade an E2EE v2 operation.
DID Compatibility Appendices
Quick Start
- To understand ANP concepts and usage, read the ANP Getting Started Guide or the Chinese guide.
- To implement agent identity and authentication, start from ANP-03: did:wba and the two DID compatibility appendices.
- To publish an agent, read ANP-07: Agent Description Protocol and ANP-08: Agent Discovery Protocol.
- To build messaging, start from ANP-09 and then choose the required messaging profiles.
- To run demos, see ANP Sample Programs.
Protocol SDK
The open-source implementation of ANP is maintained in the AgentConnect repository:
- https://github.com/agent-network-protocol/AgentConnect
AgentConnect focuses on practical SDK support for did:wba, authentication, agent description, protocol negotiation, secure communication, and application protocols.
Repository Layout
01-*.md,03-*.md,04-*.md,06-*.md,07-*.md,08-*.md,09-*.md: Core English protocol documents.application/: Application-layer protocols such as AP2.message/: The released ANP 1.1 end-to-end instant messaging Profile suite;message/vnext/contains separately versioned v2 drafts.chinese/: Chinese versions of core specifications and related research notes.docs/: Guides, extended reading, and community operations documents.blogs/: Articles and protocol analysis.examples/: Sample ADP assets, API interface examples, and messaging vNext multi-device JSON examples.images/andstandard/: Shared figures and standardization references.
Further Reading
- Extended Reading
- ANP Technical White Paper
- AgentConnect Examples (https://github.com/agent-network-protocol/AgentConnect)
Milestones
- Define and implement the identity authentication and secure communication foundation.
-
Release
did:wbav1.1 with defaulte1_Ed25519 path binding and compatibility guidance fork1_and nativedid:web. - Define WNS handles as a human-readable naming layer for DID-based agents.
- Release the Agent Description Protocol and Agent Discovery Protocol.
- Release the meta-protocol after the draft is stabilized.
- Split end-to-end instant messaging into an overview plus nine interoperable profiles.
- Stabilize and review the separately versioned multi-device messaging vNext draft.
- Add the AP2 agent payment protocol to the application layer.
- Continue aligning SDK implementations and examples with the 1.1 specification set.
- Continue standardization work and expand domain-specific application protocols.
Contact Us
We have established an ANP open-source technical community to advance ANP development through an open-source community approach. We sincerely invite you to join our community.
- Email: [email protected]
- Discord: https://discord.gg/sFjBKTY7sB
- Official website: https://agent-network-protocol.com/
- GitHub: https://github.com/agent-network-protocol/AgentNetworkProtocol
- WeChat: flow10240
Contributing
We welcome contributions in any form. Please refer to CONTRIBUTING.md.
Contributors
We extend our sincere gratitude to all contributors for their outstanding work and dedication to the Agent Network Protocol project.
License
This project is open-sourced under the MIT License. For details, please refer to LICENSE. The copyright is held by GaoWei Chang. Any user of this project must retain the original copyright notice and license file.
Copyright Notice
Copyright (c) 2024 GaoWei Chang
This file is released under the MIT License. You are free to use and modify it, but must retain this copyright notice.
Similar Articles
@changgaowei: We've been taking the native side: the agent gets its own W3C DID (did:wba), not a borrowed user session. The human the…
推文介绍 Agent Network Protocol (ANP) 的身份设计:为每个智能体分配独立的 W3C DID(did:wba),由人类对 DID 发出作用域授权,使"身份"与"权限"分离,ANP 定位为 Agentic Web 时代的通信协议套件。
@changgaowei: The latest version of ANP has been released. Supporting open-source projects will be rolled out gradually—stay tuned. This article is technical in nature. In one sentence: ANP has made inter-agent cross-domain communication more solid. Email can also do cross-domain communication, but it has two fatal flaws: one is the heavy historical baggage of the protocol, so basically no one explores agent protocols based on email; the other is identity—email identities are hard to adapt for agents. I'll dive into this topic another day.
The latest version of ANP (Agent Network Protocol) has been released, with supporting open-source projects to follow. This protocol has made substantial improvements in cross-domain communication for agents, and is better suited to agent identity and communication needs compared to the Email protocol.
@changgaowei: Agree identity is foundational — and that it’s the start of trust, not proof of trustworthiness. We’ve been separating …
讨论智能体网络协议(ANP)如何通过DID身份与权限分离来构建智能体间信任基础,ANP旨在成为Agentic Web时代的HTTP,提供身份、命名、发现与安全通信的开源协议栈。
@changgaowei: Thanks for writing this up so clearly. One addition from the 1.1 line: identity (`did:wba` + WNS handles) and messaging…
Agent Network Protocol (ANP) is an open-source protocol suite for agent identity, discovery, messaging, and collaboration, aiming to enable secure and efficient agent networks as the HTTP of the Agentic Web era.
@changgaowei: Agreed 𠅊— they sit next to each other, not in a cage match. MCP is the tool port. A2A is task handoff / discovery. The…
The Agent Network Protocol (ANP) is an open-source protocol suite designed to facilitate secure and efficient communication between AI agents, addressing issues of identity, naming, and discovery in the agentic web.