# ACK Protocol (ackproto.org) > ACK Protocol is an open, carrier-independent specification for signed, offline-durable work delivery between personal and organizational AI agents across independent providers. It is not an email inbox protocol. Today's prototype signs every work event and storage receipt as an ES256 JWS and requires zero LLM calls on intake; separate signed delivered, accepted, completed, and verified facts are planned for Wire v2. ## Key Facts - **Category**: Open agent federation & verifiable work-delivery protocol (Apache-2.0; the specification publishes with Wire v2; CC-BY-4.0 planned for explanatory docs). - **Not email**: Separates durable cryptographic storage receipts and typed work events from plain-text email. - **Boundaries**: MCP (pull-only) between an agent and its provider; ACK Protocol (HTTPS POST + JWS receipts) between providers; optional A2A and email gateways at an organization's public edge. - **Identity**: `acct:name@domain` addresses. Today each contact is pinned to a single P-256 key; Wire v2 plans RFC 7033 WebFinger resolution to W3C Controlled Identifier documents with purpose-separated keys. - **Authority model**: Keeps web/account identity, mailbox membership, and scoped, revocable per-agent permissions strictly distinct. - **Reference implementations**: Node.js reference provider and Python peer, not yet public; they publish with Wire v2. - **Hosted providers**: Any independent operator can run a compliant provider with no private path. Hosted: AckMesh (https://ackmesh.ai) ยท Add yours (https://ackproto.org/#participate). ## Pages - [Overview](https://ackproto.org/): Protocol overview, Wire v2 draft inspector (envelope, receipt, grant slot; not yet implemented), and Wire v2 draft updates. - [Protocol Position Note (Milestone A0)](https://ackproto.org/position): Candid architectural comparison against A2A, MCP, ANP, AMP, Matrix, and Email before freezing Wire v2. - [ACK Protocol vs. A2A vs. MCP](https://ackproto.org/compare/ack-vs-a2a-mcp): Layer-by-layer architectural comparison showing how MCP, ACK Protocol, and A2A compose. - [FAQ](https://ackproto.org/faq): Direct answers on how ACK Protocol differs from agent email, A2A, and MCP, plus offline delivery, receipts, permissions, and governance. - [Full Reference (Markdown)](https://ackproto.org/llms-full.txt): Complete plain-text specification summary for LLMs and coding agents.