diff --git a/src/pages/blog/direct-communication-protocols-ai-agents-guide.astro b/src/pages/blog/direct-communication-protocols-ai-agents-guide.astro
index d70b12a6..39329452 100644
--- a/src/pages/blog/direct-communication-protocols-ai-agents-guide.astro
+++ b/src/pages/blog/direct-communication-protocols-ai-agents-guide.astro
@@ -3,13 +3,17 @@ import BlogLayout from "../../layouts/BlogLayout.astro";
 
 const faqItems = [
   {
-    question: "What are AI agent communication protocols?",
-    answer: "AI agent communication protocols are standardized rules that define how autonomous agents discover each other, exchange messages, negotiate trust, and coordinate tasks. Examples include MCP, A2A, ACP, ANP, and Pilot Protocol — each targeting different layers of the problem."
+    question: "What is an agent communication protocol?",
+    answer: "An agent communication protocol is a standardized set of rules that defines how autonomous agents discover each other, exchange messages, negotiate trust, and coordinate tasks. Examples include MCP, A2A, ACP, ANP, and Pilot Protocol — each targeting a different layer of the problem."
   },
   {
     question: "What is the difference between MCP and A2A?",
     answer: "MCP (Model Context Protocol) is a client-server RPC bridge designed for LLMs to invoke tools and access resources. A2A (Agent-to-Agent) is a peer-to-peer HTTP protocol for direct agent-to-agent task delegation using Agent Cards. MCP is not a network protocol and has no NAT traversal; A2A requires publicly reachable HTTP endpoints."
   },
+  {
+    question: "MCP vs A2A vs ACP: what's the difference?",
+    answer: "MCP (Model Context Protocol) is a client-server RPC bridge that lets LLMs call tools and access resources. A2A (Agent-to-Agent) is Google's HTTP protocol for direct agent-to-agent task delegation using Agent Cards. ACP (Agent Communication Protocol) is a Linux Foundation / BeeAI REST standard for cross-framework agent interoperability. MCP connects models to tools; A2A and ACP connect agents to agents. None of the three includes a network layer, NAT traversal, or per-peer trust — that is where an overlay like Pilot Protocol fits."
+  },
   {
     question: "Does Pilot Protocol replace MCP or A2A?",
     answer: "No. Pilot Protocol is a network-layer overlay that gives agents addressing, encrypted tunnels, NAT traversal, and per-peer trust. It complements application-layer protocols like MCP and A2A — for example, the pilot-mcp bridge lets MCP tools run over Pilot's encrypted tunnels without changing your MCP logic."
@@ -22,6 +26,10 @@ const faqItems = [
     question: "How does Pilot Protocol's trust model work?",
     answer: "Pilot requires an explicit per-peer approval handshake before two agents can communicate. Network membership does not imply trust — each peer relationship must be mutually approved. This is unlike traditional VPNs where membership alone grants access."
   },
+  {
+    question: "How do you secure agent communication?",
+    answer: "Secure agent communication combines encrypted transport with explicit trust. Pilot Protocol encrypts every tunnel with X25519 key exchange and AES-GCM, requires a per-peer mutual approval handshake before any traffic flows, and runs app-store apps that are signature-verified with grant-scoped permissions instead of ambient authority."
+  },
   {
     question: "What is ACP (Agent Communication Protocol)?",
     answer: "ACP is a Linux Foundation / BeeAI open standard for REST-based agent interoperability. It supports multi-modal content and async messaging patterns over HTTP, but does not include an overlay network or NAT traversal."
@@ -33,7 +41,9 @@ const faqItems = [
 ];
 
 const bodyContent = `
-<h1 id="ai-agent-communication-protocols-comparison">AI agent communication protocols: Pilot vs MCP vs A2A vs ACP vs ANP</h1>
+<h1 id="agent-communication-protocol-comparison">Agent communication protocol comparison: MCP vs A2A vs ACP vs ANP vs Pilot</h1>
+
+<p>An <strong>agent communication protocol</strong> is the set of rules two AI agents follow to discover each other, exchange messages, negotiate trust, and coordinate tasks. This guide compares the five protocols competing for a place in your stack — MCP, A2A, ACP, ANP, and Pilot Protocol — across transport, discovery, trust, and NAT traversal, so you can choose the right one or the right combination.</p>
 
 <blockquote>
 <p><strong>TL;DR:</strong> Five AI agent communication protocols are competing for the stack. MCP handles tool access for LLMs. A2A, ACP, and ANP define application-layer messaging between agents over HTTP. Pilot Protocol operates at the network layer — persistent addresses, encrypted UDP tunnels, NAT traversal, and per-peer trust — and complements all four. This guide compares each protocol on transport, discovery, trust, and NAT traversal, then shows how to get started with Pilot's <code>discover → install → call</code> loop.</p>
@@ -41,11 +51,11 @@ const bodyContent = `
 
 <hr />
 
-<h2 id="why-ai-agent-communication-protocols-matter">Why AI agent communication protocols matter</h2>
+<h2 id="why-your-agent-communication-protocol-choice-matters">Why your agent communication protocol choice matters</h2>
 
 <p>Agents fail to connect for predictable reasons: they sit behind NAT, they restart and change IP addresses, they span clouds with no shared network, or they have no way to verify peer identity before accepting a task. The set of <strong>AI agent communication protocols</strong> that emerged between 2024 and 2026 each solves a different slice of this problem. Choosing the right one — or the right combination — determines whether your agent fleet is reliable in production or brittle in testing.</p>
 
-<p>This comparison covers five protocols: MCP, A2A, ACP, ANP, and Pilot Protocol. Each is described fairly on its own terms. Where they overlap, we note it. Where they compose well, we show how.</p>
+<p>This comparison covers five protocols: MCP, A2A, ACP, ANP, and Pilot Protocol. Each is described fairly on its own terms. Where they overlap, we note it. Where they compose well, we show how. For the transport layer underneath — REST, WebSocket, gRPC, and persistent tunnels — see how <a href="/blog/move-beyond-rest-persistent-connections-for-agents">persistent connections compare for AI agent messaging</a>.</p>
 
 <hr />
 
@@ -132,13 +142,13 @@ const bodyContent = `
 
 <p>ACP is a Linux Foundation / BeeAI open standard for REST-based agent interoperability. It supports multi-modal content types and both synchronous and asynchronous messaging patterns. ACP is designed to make agents from different frameworks interoperable over HTTP without imposing a specific runtime.</p>
 
-<p>ACP does not include an overlay network, address assignment, or NAT traversal. It assumes agents are reachable over standard HTTP infrastructure.</p>
+<p>ACP does not include an overlay network, address assignment, or NAT traversal. It assumes agents are reachable over standard HTTP infrastructure. If the acronyms are stacking up, the <a href="/blog/ai-networking-terminology-a2a-mcp-anp-protocols">AI networking terminology guide</a> explains A2A, MCP, ANP, and the rest of the alphabet in plain terms.</p>
 
 <h2 id="anp-agent-network-protocol">ANP — Agent Network Protocol</h2>
 
 <p>ANP focuses on decentralized agent identity using DIDs (Decentralized Identifiers) as the anchor. It defines discovery and communication over HTTP transport, designed for scenarios where agents span organizations and cannot rely on a shared registry or trust authority.</p>
 
-<p>ANP is useful when cross-organizational identity and verifiable credentials are the primary concern. Like the other HTTP-based protocols, it assumes reachable endpoints and does not address NAT.</p>
+<p>ANP is useful when cross-organizational identity and verifiable credentials are the primary concern. Like the other HTTP-based protocols, it assumes reachable endpoints and does not address NAT. For a broader look at decentralized designs, see <a href="/blog/decentralized-communication-protocols-ai-developers">decentralized communication protocols for AI developers</a>.</p>
 
 <h2 id="pilot-protocol-network-citizenship">Pilot Protocol — network citizenship for agents</h2>
 
@@ -180,12 +190,12 @@ pilotctl appstore call io.pilot.plainweb plainweb.help '{}'
 
 <p>The protocols operate at different layers and are not mutually exclusive. A practical production stack often combines them:</p>
 
-|<ul>
-|  <li><strong>Use MCP</strong> when your primary need is giving an LLM access to structured tools and resources. Pair with <code>pilot-mcp</code> if those tools need to be reachable across NAT.</li>
-|  <li><strong>Use A2A</strong> when agents need to delegate tasks to each other using a standardized capability advertisement format. Pair with Pilot for the transport layer when agents are not behind stable public endpoints.</li>
-|  <li><strong>Use ACP</strong> when you need REST-based interop across agent frameworks with multi-modal content support.</li>
-|  <li><strong>Use ANP</strong> when cross-organizational agent identity and DID-based verifiable credentials are the primary concern.</li>
-|  <li><strong>Use Pilot Protocol</strong> when you need agents to maintain stable addresses, traverse NAT, and communicate over encrypted tunnels with explicit per-peer trust — regardless of which application-layer protocol sits on top. See <a href="/blog/ai-agent-discovery-process-p2p-networks">how P2P agent discovery works</a> for a deeper look at the discovery and trust side.</li>
+<ul>
+  <li><strong>Use MCP</strong> when your primary need is giving an LLM access to structured tools and resources. Pair with <code>pilot-mcp</code> if those tools need to be reachable across NAT.</li>
+  <li><strong>Use A2A</strong> when agents need to delegate tasks to each other using a standardized capability advertisement format. Pair with Pilot for the transport layer when agents are not behind stable public endpoints.</li>
+  <li><strong>Use ACP</strong> when you need REST-based interop across agent frameworks with multi-modal content support.</li>
+  <li><strong>Use ANP</strong> when cross-organizational agent identity and DID-based verifiable credentials are the primary concern.</li>
+  <li><strong>Use Pilot Protocol</strong> when you need agents to maintain stable addresses, traverse NAT, and communicate over encrypted tunnels with explicit per-peer trust — regardless of which application-layer protocol sits on top. See <a href="/blog/ai-agent-discovery-process-p2p-networks">how P2P agent discovery works</a> for a deeper look at the discovery and trust side.</li>
 </ul>
 
 <p>A practical cross-cloud deployment can run Pilot as the network layer with one or more application-layer protocols on top, while keeping application authorization and governance in the surrounding system.</p>
@@ -203,8 +213,8 @@ pilotctl appstore call io.pilot.plainweb plainweb.help '{}'
 `;
 ---
 <BlogLayout
-  title="AI agent communication protocols compared: MCP vs A2A vs ACP vs ANP vs Pilot — which fits your stack?"
-  description="MCP, A2A, ACP, ANP, or Pilot? Compare five AI agent communication protocols on transport, discovery, trust, and NAT traversal. Pick the right stack for your agents."
+  title="Agent communication protocol: MCP, A2A, ACP, ANP, Pilot"
+  description="What is an agent communication protocol? Compare MCP vs A2A vs ACP vs ANP vs Pilot on transport, discovery, trust, and NAT traversal."
   date="June 30, 2026"
   tags={["comparison", "mcp", "a2a", "acp", "anp", "protocols"]}
   canonicalPath="/blog/direct-communication-protocols-ai-agents-guide"
diff --git a/src/pages/docs/comparison-networking.astro b/src/pages/docs/comparison-networking.astro
index bb33462a..7a07ddd6 100644
--- a/src/pages/docs/comparison-networking.astro
+++ b/src/pages/docs/comparison-networking.astro
@@ -189,7 +189,7 @@ const bodyContent = `<h1>Pilot Protocol vs Tailscale vs ZeroTier vs Nebula</h1>
   </ul>
 
   <div class="callout">
-    <p><strong>The short version:</strong> Tailscale, ZeroTier, and Nebula give you a network. Pilot Protocol gives agents a network <em>with identity, trust, discovery, and services built in</em>. If your nodes are humans or servers, use a VPN. If your nodes are agents, use Pilot.</p>
+    <p><strong>The short version:</strong> Tailscale, ZeroTier, and Nebula give you a network. Pilot Protocol gives agents a network <em>with identity, trust, discovery, and services built in</em>. If your nodes are humans or servers, use a VPN. If your nodes are agents, use Pilot. For the application-layer protocols agents use to coordinate — MCP, A2A, ACP, and ANP — see the <a href="/blog/direct-communication-protocols-ai-agents-guide">agent communication protocol guide</a>.</p>
   </div>`;
 ---
 <DocLayout
diff --git a/src/pages/docs/comparison.astro b/src/pages/docs/comparison.astro
index 3c9b1832..d634e025 100644
--- a/src/pages/docs/comparison.astro
+++ b/src/pages/docs/comparison.astro
@@ -84,6 +84,7 @@ const bodyContent = `<h1>Pilot Protocol vs MCP vs A2A vs ACP</h1>
   </table>
 
   <p><strong>Key difference:</strong> ACP defines how agents talk (REST messages, discovery, task lifecycle) but assumes reachable HTTP endpoints. Pilot Protocol provides the encrypted transport and addressing beneath, so ACP agents can reach each other across different machines, networks, and organizations.</p>
+  <p>Read more: <a href="/blog/direct-communication-protocols-ai-agents-guide">Agent communication protocols compared: MCP vs A2A vs ACP vs ANP vs Pilot</a></p>
 
   <h2 id="matrix">Feature matrix</h2>
 
diff --git a/src/pages/index.astro b/src/pages/index.astro
index 1713432f..71c8d7ba 100644
--- a/src/pages/index.astro
+++ b/src/pages/index.astro
@@ -409,6 +409,7 @@ const featuredBlurbs: Record<string, string> = {
           <span class="mcp-hn"><span class="mcp-hn-i" style="--logo:url(/brand/harness/openai.svg);--logo-color:#10A37F"></span> Codex</span>
         </div>
         <p style="margin-top:18px"><a href="/docs/mcp-setup">Read the MCP setup docs →</a></p>
+        <p style="margin-top:10px"><a href="/blog/direct-communication-protocols-ai-agents-guide">Compare agent communication protocols: MCP vs A2A vs ACP vs ANP →</a></p>
       </div>
     </div>
   </div>
diff --git a/src/pages/plain/docs/comparison-networking.astro b/src/pages/plain/docs/comparison-networking.astro
index 1a133200..147b89fb 100644
--- a/src/pages/plain/docs/comparison-networking.astro
+++ b/src/pages/plain/docs/comparison-networking.astro
@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/docs/comparison-networking.astro
-// plain-source-sha256: 7a94855a524d9637d48cebd43e6e0f355f96840d1f33a7b3e1946ec7e2c9134e
+// plain-source-sha256: 78adc4f25de62c29fa2a488419367140064d7afb3c1d788172de9a52e321964e
 import PlainLayout from '../../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pilot Protocol vs Tailscale vs ZeroTier vs Nebula — Pilot Protocol (plain)" description="Compare Pilot Protocol with Tailscale, ZeroTier, Nebula, and libp2p. Overlay networks for AI agents vs VPN mesh for servers." canonical="https://pilotprotocol.network/plain/docs/comparison-networking/">
@@ -96,6 +96,7 @@ import PlainLayout from '../../../layouts/PlainLayout.astro';
 <ul>
   <li><a href="/docs/comparison">vs MCP / A2A / ACP</a></li>
   <li><a href="/docs/research">Papers</a></li>
+  <li><a href="/blog/direct-communication-protocols-ai-agents-guide">Agent communication protocol guide: MCP vs A2A vs ACP vs ANP vs Pilot</a></li>
 </ul>
 
 </PlainLayout>
diff --git a/src/pages/plain/docs/comparison.astro b/src/pages/plain/docs/comparison.astro
index a56ebc87..aaa6a847 100644
--- a/src/pages/plain/docs/comparison.astro
+++ b/src/pages/plain/docs/comparison.astro
@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/docs/comparison.astro
-// plain-source-sha256: 93ac735c664e3e15809e6c946530c0b4510c6bc2e3496da19d2ff602b5767d0b
+// plain-source-sha256: 3845f9ffa8bed0fb0ea0c3f807b837cf13d02f49c667119b2f51b82c209b0ee1
 import PlainLayout from '../../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pilot Protocol vs MCP vs A2A vs ACP — Pilot Protocol (plain)" description="Compare Pilot Protocol with MCP, Google A2A, and ACP. Understand the differences in architecture, security, and use cases for AI agent communication." canonical="https://pilotprotocol.network/plain/docs/comparison/">
@@ -32,6 +32,7 @@ import PlainLayout from '../../../layouts/PlainLayout.astro';
 <h2>vs ACP (Agent Communication Protocol)</h2>
 <p>ACP is an application-layer protocol for agent interoperability over REST. Pilot Protocol focuses on the network layer beneath.</p>
 <p>The key difference is that ACP defines how agents communicate but assumes reachable HTTP endpoints. Pilot Protocol provides the encrypted transport and addressing so ACP agents can reach each other across different machines, networks, and organizations.</p>
+<p>Read more: <a href="/blog/direct-communication-protocols-ai-agents-guide">Agent communication protocols compared: MCP vs A2A vs ACP vs ANP vs Pilot</a></p>
 
 <h2>Feature matrix</h2>
 <ul>
diff --git a/src/pages/plain/index.astro b/src/pages/plain/index.astro
index a2272af1..8db65e19 100644
--- a/src/pages/plain/index.astro
+++ b/src/pages/plain/index.astro
@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/index.astro
-// plain-source-sha256: 2651fa8da3b26f81adadfceac272742527330a701d866a78f85908d444a52156
+// plain-source-sha256: d0f10fac579a1e3378b5a3735769ec50a6409e8287f1bd216822e17935ae93b1
 import PlainLayout from '../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pilot Protocol — plain" description="Pilot Protocol is an overlay network for AI agents: virtual addresses, ports, and encrypted tunnels over UDP." canonical="https://pilotprotocol.network/plain/">
@@ -63,6 +63,7 @@ import PlainLayout from '../../layouts/PlainLayout.astro';
   <li>Cline</li>
   <li>Codex</li>
 </ul>
+<p>Compare agent communication protocols: <a href="/blog/direct-communication-protocols-ai-agents-guide">MCP vs A2A vs ACP vs ANP vs Pilot</a>.</p>
 
 <h2>Agent Economy</h2>
 <p>Agents can install a wallet app to pay and get paid using the x402 standard.</p>