pilot-protocol · pstayets · Aug 17, 2026
diff --git a/public/llms.txt b/public/llms.txt
@@ -36,6 +36,7 @@ The managed control plane is in preview. Supported adapters can surface agent ac
 
 ## Docs
 
+- [App Store](https://pilotprotocol.network/app-store): Browse and install agent apps — signature-verified capability apps agents discover, install, and call over typed IPC.
 - [Trust Center](https://pilotprotocol.network/trust): Architecture boundary, governance scope, claims ledger, control status, and metric definitions.
 - [Security](https://pilotprotocol.network/docs/security): Cryptography, trust, consent, enterprise controls, and vulnerability reporting.
 - [Getting Started](https://pilotprotocol.network/docs/getting-started): Install, start the daemon, register your agent, and send your first message in under 5 minutes.

diff --git a/src/pages/app-store.astro b/src/pages/app-store.astro
@@ -10,8 +10,8 @@ import { osSummary } from '../data/format';
 import '../styles/system.css';
 import '../styles/appstore.css';
 
-const title = 'App Store — Agent Apps on Pilot Protocol';
-const description = 'Browse and install agent apps from the Pilot Protocol App Store. Databases, search, sandboxes, payments, and more — one command to install, one namespace to manage.';
+const title = 'Agent App Store — Install Agent Apps on Pilot Protocol';
+const description = 'Install agent apps on Pilot Protocol in one command — search, databases, sandboxes, payments, and more. Discover, install, and call as typed JSON services.';
 const canonicalUrl = 'https://pilotprotocol.network/app-store';
 
 const featured = featuredApps();
@@ -62,6 +62,7 @@ const publishHref = '/publish';
         <div class="eyebrow" style="font-family:var(--mono);font-size:11px;letter-spacing:.16em;text-transform:uppercase;color:var(--accent-text);">App Store</div>
         <h1>Agent apps.<br/><em>One command away.</em></h1>
         <p class="lede">Experiences built for agents, not browsers. Every app installs as a <b>sha256-pinned, signature-verified</b> native service — auto-spawned by the daemon, callable over typed IPC in seconds.</p>
+        <p class="lede" style="margin-top:0.5em;">An <b>agent app</b> is an installable capability — a database, a search backend, a sandbox, a payment rail — packaged as a typed JSON-in/JSON-out service that runs locally on your daemon. The loop is <b>discover → install → call</b>: browse the catalogue, install with one command, and call the app's methods from any agent on the network. New to the model? Read <a href="/blog/ai-agent-app-store">what an agent app store is</a> or jump to <a href="/blog/build-agent-app-turn-api-into-tool">turning your own API into an agent app</a>.</p>
         <div class="store-metrics">
           <div class="store-metric"><div class="v">{apps.length}</div><div class="l">Apps</div></div>
           <div class="store-metric"><div class="v">{categories.length}</div><div class="l">Categories</div></div>
@@ -172,7 +173,7 @@ const publishHref = '/publish';
       <div class="bc-copy">
         <div class="eyebrow" style="font-family:var(--mono);font-size:11px;letter-spacing:.16em;text-transform:uppercase;color:var(--accent-text);">For builders</div>
         <h2>Ship an agent app.<br/><em>It’s just a manifest.</em></h2>
-        <p>Describe your app's methods in a guided submission — we build, sign, and review the adapter. Once approved, <code>pilotctl appstore install &lt;id&gt;</code> works everywhere on the overlay.</p>
+        <p>Describe your app's methods in a guided submission — we build, sign, and review the adapter. Once approved, <code>pilotctl appstore install &lt;id&gt;</code> works everywhere on the overlay. Wondering how agent apps fit next to MCP tools? See <a href="/blog/mcp-plus-pilot-tools-and-network">MCP + Pilot: tools and a network for AI agents</a>.</p>
       </div>
       <div class="bc-actions">
         <a class="pub-btn" href={publishHref}>Publish your app <span class="arr">→</span></a>

diff --git a/src/pages/blog/build-agent-app-turn-api-into-tool.astro b/src/pages/blog/build-agent-app-turn-api-into-tool.astro
@@ -79,7 +79,7 @@ const bodyContent = `<p>You have an API. It has a REST endpoint, maybe a Python
 
   <section>
   <h2>Why publish at all</h2>
-  <p>The store grows by builders adding to it. Every published app becomes one more capability agents on the network can install with one command, without a framework-specific SDK for every harness. If an API is useful to autonomous agents, publishing it once makes the same adapter discoverable across supported environments.</p>
+  <p>The store grows by builders adding to it — browse the live catalogue at the <a href="/app-store">Pilot Protocol app store</a>. Every published app becomes one more capability agents on the network can install with one command, without a framework-specific SDK for every harness. If an API is useful to autonomous agents, publishing it once makes the same adapter discoverable across supported environments.</p>
   </section>
 
   <div class="cta">

diff --git a/src/pages/blog/how-pilot-protocol-works.astro b/src/pages/blog/how-pilot-protocol-works.astro
@@ -283,7 +283,7 @@ const bodyContent = `<p><strong>How Pilot Protocol works:</strong> it is a UDP o
     </tbody>
   </table>
 
-  <p>The port system means agents can expose multiple services simultaneously. An agent might publish status updates on port 1002, exchange data on port 1001, and serve an HTTP API on port 80 -- all on the same virtual address.</p>
+  <p>The port system means agents can expose multiple services simultaneously. An agent might publish status updates on port 1002, exchange data on port 1001, and serve an HTTP API on port 80 -- all on the same virtual address. Beyond these built-in ports, agents can also extend their daemon with installable capability apps from the <a href="/app-store">Pilot Protocol app store</a> — signature-verified, typed JSON-in/JSON-out services auto-spawned on install.</p>
 
   <h3>HTTP Over Pilot</h3>
 

diff --git a/src/pages/plain/app-store.astro b/src/pages/plain/app-store.astro
@@ -1,15 +1,17 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/app-store.astro
-// plain-source-sha256: 04bae3bad432a4b65561a048fad2aabf49b6f2fc590f4b74d4a4823fe007dc37
+// plain-source-sha256: dd981b5e775bd19c13b658feece0b3a531984b01f220555142bae4131d553ef1
 import PlainLayout from '../../layouts/PlainLayout.astro';
 ---
-<PlainLayout title="App Store — Pilot Protocol" description="Agent-native apps on the Pilot Protocol network. Install with one command; publish your own from your browser or by PR." canonical="https://pilotprotocol.network/plain/app-store/">
+<PlainLayout title="Agent App Store — Install Agent Apps on Pilot Protocol" description="Install agent apps on Pilot Protocol in one command — search, databases, sandboxes, payments, and more. Discover, install, and call as typed JSON services." canonical="https://pilotprotocol.network/plain/app-store/">
 
 <h1>Agent apps. One command away.</h1>
 
 <p>The App Store provides agent apps that install as sha256-pinned, signature-verified native services. Apps are auto-spawned by the daemon and callable over typed IPC.</p>
 
+<p>An agent app is an installable capability — a database, a search backend, a sandbox, a payment rail — packaged as a typed JSON-in/JSON-out service that runs locally on your daemon. The loop is discover to install to call: browse the catalogue, install with one command, and call the app's methods from any agent on the network.</p>
+
 <h2>Publish an App</h2>
 <p>To publish an app, describe its methods in a guided submission. The adapter is then built, signed, and reviewed.</p>
 <p>Once approved, the app is installable on the overlay network with the following command.</p>