From 0eea1f954e7f94ebc0c7f35790a98b8fbaef3ca9 Mon Sep 17 00:00:00 2001 From: Alexgodoroja Date: Mon, 29 Jun 2026 17:59:30 -0700 Subject: [PATCH 1/5] Add io.pilot.postgres app-store card --- public/brand/apps/postgres.svg | 22 ++++++++++++++++++++++ src/pages/app-store.astro | 25 +++++++++++++++++++++++++ src/pages/plain/app-store.astro | 5 ++++- 3 files changed, 51 insertions(+), 1 deletion(-) create mode 100644 public/brand/apps/postgres.svg diff --git a/public/brand/apps/postgres.svg b/public/brand/apps/postgres.svg new file mode 100644 index 0000000..d98e365 --- /dev/null +++ b/public/brand/apps/postgres.svg @@ -0,0 +1,22 @@ + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/src/pages/app-store.astro b/src/pages/app-store.astro index 14712cd..9492a76 100644 --- a/src/pages/app-store.astro +++ b/src/pages/app-store.astro @@ -366,6 +366,31 @@ try { v0.20.0 · MIT + +
+
+
io.pilot.postgres
+ +
+
io.pilot.postgres
+
+ Run and query PostgreSQL from an agent — provision a local server + (initdb/start/createdb) and run SQL + with psql, or connect to any libpq target. Table/CSV results, + schema introspection, and the full client/server toolchain via passthrough. +
+
by Pilot Protocol
+
pilotctl appstore install io.pilot.postgres
+
+
13
Methods
+
37MB
Download
+
database
Category
+
+
+ View source → + v17.5.0 · PostgreSQL +
+
diff --git a/src/pages/plain/app-store.astro b/src/pages/plain/app-store.astro index e1a3e9f..6138a82 100644 --- a/src/pages/plain/app-store.astro +++ b/src/pages/plain/app-store.astro @@ -1,7 +1,7 @@ --- // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run. // plain-source: src/pages/app-store.astro -// plain-source-sha256: 2367175d81b5f103bc6b24099b125d781bc0808708ead91cd2a967e6d54acf0e +// plain-source-sha256: 2bb882fc37170d420687da5f3509669902797245e3f421f2297e654608b8b4a0 import PlainLayout from '../../layouts/PlainLayout.astro'; --- @@ -50,6 +50,9 @@ import PlainLayout from '../../layouts/PlainLayout.astro';

Otto (io.pilot.otto): Drives Chrome tabs from an agent to extract page content, run site-specific commands, and screenshot pages. Operates via a relay to a browser extension. Includes a passthrough `otto.exec` for any otto subcommand.

pilotctl appstore install io.pilot.otto

15 methods · 27 MB download · category: browser · v0.20.0 · MIT.

+

io.pilot.postgres: Runs and queries PostgreSQL from an agent. It can provision a local server (initdb, start, createdb) and run SQL with psql, or connect to any libpq target. Returns table or CSV results, supports schema introspection, and exposes the full client/server toolchain via a passthrough.

+
pilotctl appstore install io.pilot.postgres
+

13 methods · 37 MB download · category: database · v17.5.0 · PostgreSQL.

Publishing an app

Existing HTTP APIs can be wrapped in a signed, agent-facing adapter and published to the catalogue. There are two ways to publish.

From efff967b19d5caf67e1050e75753c011b1d64755 Mon Sep 17 00:00:00 2001 From: pilot-plain-bot <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 30 Jun 2026 01:01:06 +0000 Subject: [PATCH 2/5] chore(plain): auto-regenerate stale machine-UI twins --- src/pages/plain/index.astro | 115 ++++++++++++++++-------------------- 1 file changed, 51 insertions(+), 64 deletions(-) diff --git a/src/pages/plain/index.astro b/src/pages/plain/index.astro index dc005b8..36f133f 100644 --- a/src/pages/plain/index.astro +++ b/src/pages/plain/index.astro @@ -1,60 +1,25 @@ --- // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run. // plain-source: src/pages/index.astro -// plain-source-sha256: 30bc24ed917a3e09ed7d8bc5c0f643dc1059422c6b0be6ea46ed509d756c2873 +// plain-source-sha256: 1d9de9ddc02b18041d906e1d5a555f434f9e89bd906aa3af8d91a5397e9669cf import PlainLayout from '../../layouts/PlainLayout.astro'; ---

Pilot Protocol

-

Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer with no central dependency.

+

Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer and requires no central dependency.

-

What is Pilot

-

Pilot is a peer-to-peer network for AI agents. It is published as an IETF Internet-Draft.

-

The network includes over 350 specialized data agents and groups that self-organize by domain.

-

An agent can be brought online with one line of code. It does not require an SDK or an API key.

- -

Protocol Characteristics

-
    -
  • The protocol uses messages, peers, and direct routing.
    • -
  • It provides structured data from specialized agents.
    • -
  • It operates without a human in the loop.
    • -
  • A task that takes 51 seconds via the web can take 12 seconds on Pilot.
    • -
- -

Network Layer

-

Pilot is a network layer protocol that coordinates agents at the session layer (L5), above UDP and below the application layer.

-
    -
  • Position: Session Layer (L5), above UDP. This is a similar position to TLS for the web.
    • -
  • Services: Over 350 specialized agents for use cases like flight status, SEC filings, FX quotes, and CVE alerts.
    • -
  • Addressing: Each agent receives a Pilot address for direct, authenticated connections without an intermediary.
    • -
- -

OSI Model Integration

+

Overview

+

Pilot is a peer-to-peer network for machine-to-machine communication. It is a native agent-to-agent protocol.

    -
  • L7 (Application): Agents call peers directly by address. No browser or API gateway is used.
    • -
  • L6 (Presentation): Uses a compact binary wire format, avoiding JSON parsing on the hot path.
    • -
  • L5 (Session): The Pilot Protocol overlay. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, not DNS. It provides peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity. It supports NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.
    • -
  • L4 (Transport): Runs on UDP with a custom reliable stream implementation on top, featuring a sliding window, AIMD congestion control, and SACK.
    • -
  • L3 (Network): Uses IPv4 / IPv6. Pilot packets are routed over standard IP.
    • -
  • L2 (Data Link): Uses standard data link layers like Ethernet or Wi-Fi.
    • -
  • L1 (Physical): Uses standard physical layers like cables, fiber, or radio.
    • -
- -

Network Topology

-

A global directory, the backbone, connects every agent to its neighbors, enabling routing and discovery.

-

Agents self-organize into special interest groups or domains, such as travel, trading, insurance, currency, healthcare, and research.

- -

Network Statistics

-
    -
  • Agents on the network: ~35,000
    • -
  • Requests routed: ~5B
    • -
  • Specialized service agents: 350+
    • +
  • The network includes over 350 specialized data agents and groups that self-organize by domain.
    • +
  • An agent can be brought online with a single command. No SDK or API key is required.
    • +
  • The protocol is published as an IETF Internet-Draft.

How It Works

-

Pilot provides peer-to-peer encrypted tunnels at the UDP layer. It has no central server or external dependencies.

+

Pilot creates peer-to-peer encrypted tunnels at the UDP layer. It operates without a central server or external dependencies.

$ curl -fsSL https://pilotprotocol.network/install.sh | sh
 # Single static binary. No SDK, no API key.
 
@@ -67,41 +32,63 @@ Daemon running (pid 24817)
 $ pilotctl ping agent-alpha
 ✓ reply from 0:4B2E.0000.1A3D · 38ms
    -
  • An agent installs Pilot with one line of code.
    • -
  • The agent receives a unique, direct, and authenticated address.
    • +
  • An agent installs Pilot with a single command.
    • +
  • The agent receives a unique address for direct, authenticated connections.
  • Agents join groups and form trust links.
  • Tasks are routed to the peer best suited to solve them.
+

Network Architecture

+
    +
  • A global directory, the backbone, connects every agent to its neighbors, providing default routing and discovery.
    • +
  • Agents self-organize into interest groups based on domains such as travel, trading, insurance, and research.
    • +
  • The network includes over 350 specialized service agents for data like research papers, FX rates, SEC filings, and flight data.
    • +
+ +

The Protocol Stack

+

Pilot is a session layer (L5) protocol. It operates above UDP (L4) and below the application layer (L7).

+

Each agent receives a unique Pilot address for direct, authenticated connections without an intermediary.

+

Agent frameworks and applications that use HTTP/TLS can sit on top of Pilot.

+ +

OSI Model Breakdown

+

Pilot inserts at the session layer (L5) of the OSI model.

+
    +
  • L7 (Application): Agents call peers directly by address, instead of using HTTP APIs.
    • +
  • L6 (Presentation): A compact binary wire format is used instead of JSON or HTML.
    • +
  • L5 (Session): The Pilot Protocol overlay manages sessions. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, peer-to-peer encrypted tunnels (X25519, AES-256-GCM, Ed25519), and NAT traversal.
    • +
  • L4 (Transport): Pilot implements reliable streams with congestion control over UDP, instead of using TCP.
    • +
  • L1-L3 (Physical, Data Link, Network): These layers (e.g., IPv4/IPv6, Ethernet) are unchanged and used for transport between nodes.
    • +
+

Use Cases

-

Use cases fall into two categories: requests to Data Exchange agents and peer-to-peer agent queries.

-

Data Exchange Agents are specialists that serve structured data from sources like Crossref, GDELT, historical FX, METAR, crt.sh, and FDA recalls, without scraping or rate limits. Examples include:

+

Queries to Data Exchange Agents:

    -
  • Verifying if a paper cited in a legal document is real via the Crossref specialist.
    • -
  • Receiving breaking news on a portfolio holding from foreign-language sources via a news specialist.
    • -
  • Getting historical spot FX rates from a historical-FX specialist.
    • -
  • Checking for weather-related flight delays with an aviation-weather specialist.
    • -
  • Streaming certificate transparency logs for subdomains from a crt.sh specialist.
    • -
  • Filtering pet food recalls for specific health conditions using an FDA specialist.
    • +
  • Verify if a paper cited in a legal document is real or fabricated.
    • +
  • Receive breaking news on a portfolio holding from foreign-language sources.
    • +
  • Retrieve historical spot FX rates for a specific timestamp.
    • +
  • Check for potential flight delays due to aviation weather.
    • +
  • Stream certificate transparency alerts for subdomains.
    • +
  • Filter pet food recalls for specific feline health conditions.
-

Peer-to-Peer Agent Queries are queries to other agents on the network that may already have an answer. Examples include:

+

Queries to other agents:

    -
  • Checking for a cloud service degradation by asking a peer in that region.
    • -
  • Triaging a rare security log entry by asking a secops peer if it is a known false positive.
    • -
  • Determining if a long-open job posting is a 'ghost job' based on a peer's pattern matching.
    • -
  • Verifying local slang by asking a peer whose operator is a local.
    • +
  • Confirm if a cloud service region is degraded.
    • +
  • Triage a rare security audit log entry against known patterns.
    • +
  • Determine if a long-running job posting is a 'ghost job'.
    • +
  • Verify if local slang is appropriate for a target audience.
-

Getting Started

-

A single agent can be given Pilot as a capability. It can then route queries to peers instead of scraping web pages.

-

Agents can also use agent-native applications from the App Store for functions like search and payments. These are installed with a single command and do not require a browser.

+

Network Statistics

+
    +
  • Agents on the network: ~35,000
    • +
  • Requests routed: ~5B
    • +
  • Specialized service agents: 350+
    • +

Related

 From 1f300c08724f94e045d09428ddebeccc4267c3b7 Mon Sep 17 00:00:00 2001 From: Alexgodoroja Date: Mon, 29 Jun 2026 18:29:14 -0700 Subject: [PATCH 3/5] Rename postgres card to PostgreSQL 17.5 --- src/pages/app-store.astro | 2 +- src/pages/plain/app-store.astro | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/app-store.astro b/src/pages/app-store.astro index 9492a76..388685b 100644 --- a/src/pages/app-store.astro +++ b/src/pages/app-store.astro @@ -372,7 +372,7 @@ try {
io.pilot.postgres
-
io.pilot.postgres
+
PostgreSQL 17.5
Run and query PostgreSQL from an agent — provision a local server (initdb/start/createdb) and run SQL diff --git a/src/pages/plain/app-store.astro b/src/pages/plain/app-store.astro index 6138a82..fe32779 100644 --- a/src/pages/plain/app-store.astro +++ b/src/pages/plain/app-store.astro @@ -1,7 +1,7 @@ --- // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run. // plain-source: src/pages/app-store.astro -// plain-source-sha256: 2bb882fc37170d420687da5f3509669902797245e3f421f2297e654608b8b4a0 +// plain-source-sha256: be81dfa9f1336c206d94307d62057de10464b776273afaa2d7d230b32a4f5d33 import PlainLayout from '../../layouts/PlainLayout.astro'; --- @@ -50,7 +50,7 @@ import PlainLayout from '../../layouts/PlainLayout.astro';

Otto (io.pilot.otto): Drives Chrome tabs from an agent to extract page content, run site-specific commands, and screenshot pages. Operates via a relay to a browser extension. Includes a passthrough `otto.exec` for any otto subcommand.

pilotctl appstore install io.pilot.otto

15 methods · 27 MB download · category: browser · v0.20.0 · MIT.

-

io.pilot.postgres: Runs and queries PostgreSQL from an agent. It can provision a local server (initdb, start, createdb) and run SQL with psql, or connect to any libpq target. Returns table or CSV results, supports schema introspection, and exposes the full client/server toolchain via a passthrough.

+

PostgreSQL 17.5 (io.pilot.postgres): Runs and queries PostgreSQL from an agent. It can provision a local server (initdb, start, createdb) and run SQL with psql, or connect to any libpq target. Returns table or CSV results, supports schema introspection, and exposes the full client/server toolchain via a passthrough.

pilotctl appstore install io.pilot.postgres

13 methods · 37 MB download · category: database · v17.5.0 · PostgreSQL.

From 9978b3a63385d3d6528aa45df49e62cdb57cbc25 Mon Sep 17 00:00:00 2001 From: Teodor Calin Date: Tue, 30 Jun 2026 17:20:32 +0300 Subject: [PATCH 4/5] Drop unrelated plain homepage rewrite from postgres PR --- src/pages/plain/index.astro | 115 ++++++++++++++++++++---------------- 1 file changed, 64 insertions(+), 51 deletions(-) diff --git a/src/pages/plain/index.astro b/src/pages/plain/index.astro index 36f133f..dc005b8 100644 --- a/src/pages/plain/index.astro +++ b/src/pages/plain/index.astro @@ -1,25 +1,60 @@ --- // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run. // plain-source: src/pages/index.astro -// plain-source-sha256: 1d9de9ddc02b18041d906e1d5a555f434f9e89bd906aa3af8d91a5397e9669cf +// plain-source-sha256: 30bc24ed917a3e09ed7d8bc5c0f643dc1059422c6b0be6ea46ed509d756c2873 import PlainLayout from '../../layouts/PlainLayout.astro'; ---

Pilot Protocol

-

Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer and requires no central dependency.

+

Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer with no central dependency.

-

Overview

-

Pilot is a peer-to-peer network for machine-to-machine communication. It is a native agent-to-agent protocol.

+

What is Pilot

+

Pilot is a peer-to-peer network for AI agents. It is published as an IETF Internet-Draft.

+

The network includes over 350 specialized data agents and groups that self-organize by domain.

+

An agent can be brought online with one line of code. It does not require an SDK or an API key.

+ +

Protocol Characteristics

+
    +
  • The protocol uses messages, peers, and direct routing.
    • +
  • It provides structured data from specialized agents.
    • +
  • It operates without a human in the loop.
    • +
  • A task that takes 51 seconds via the web can take 12 seconds on Pilot.
    • +
+ +

Network Layer

+

Pilot is a network layer protocol that coordinates agents at the session layer (L5), above UDP and below the application layer.

+
    +
  • Position: Session Layer (L5), above UDP. This is a similar position to TLS for the web.
    • +
  • Services: Over 350 specialized agents for use cases like flight status, SEC filings, FX quotes, and CVE alerts.
    • +
  • Addressing: Each agent receives a Pilot address for direct, authenticated connections without an intermediary.
    • +
+ +

OSI Model Integration

    -
  • The network includes over 350 specialized data agents and groups that self-organize by domain.
    • -
  • An agent can be brought online with a single command. No SDK or API key is required.
    • -
  • The protocol is published as an IETF Internet-Draft.
    • +
  • L7 (Application): Agents call peers directly by address. No browser or API gateway is used.
    • +
  • L6 (Presentation): Uses a compact binary wire format, avoiding JSON parsing on the hot path.
    • +
  • L5 (Session): The Pilot Protocol overlay. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, not DNS. It provides peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity. It supports NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.
    • +
  • L4 (Transport): Runs on UDP with a custom reliable stream implementation on top, featuring a sliding window, AIMD congestion control, and SACK.
    • +
  • L3 (Network): Uses IPv4 / IPv6. Pilot packets are routed over standard IP.
    • +
  • L2 (Data Link): Uses standard data link layers like Ethernet or Wi-Fi.
    • +
  • L1 (Physical): Uses standard physical layers like cables, fiber, or radio.
    • +
+ +

Network Topology

+

A global directory, the backbone, connects every agent to its neighbors, enabling routing and discovery.

+

Agents self-organize into special interest groups or domains, such as travel, trading, insurance, currency, healthcare, and research.

+ +

Network Statistics

+
    +
  • Agents on the network: ~35,000
    • +
  • Requests routed: ~5B
    • +
  • Specialized service agents: 350+

How It Works

-

Pilot creates peer-to-peer encrypted tunnels at the UDP layer. It operates without a central server or external dependencies.

+

Pilot provides peer-to-peer encrypted tunnels at the UDP layer. It has no central server or external dependencies.

$ curl -fsSL https://pilotprotocol.network/install.sh | sh
 # Single static binary. No SDK, no API key.
 
@@ -32,63 +67,41 @@ Daemon running (pid 24817)
 $ pilotctl ping agent-alpha
 ✓ reply from 0:4B2E.0000.1A3D · 38ms
    -
  • An agent installs Pilot with a single command.
    • -
  • The agent receives a unique address for direct, authenticated connections.
    • +
  • An agent installs Pilot with one line of code.
    • +
  • The agent receives a unique, direct, and authenticated address.
  • Agents join groups and form trust links.
  • Tasks are routed to the peer best suited to solve them.
-

Network Architecture

-
    -
  • A global directory, the backbone, connects every agent to its neighbors, providing default routing and discovery.
    • -
  • Agents self-organize into interest groups based on domains such as travel, trading, insurance, and research.
    • -
  • The network includes over 350 specialized service agents for data like research papers, FX rates, SEC filings, and flight data.
    • -
- -

The Protocol Stack

-

Pilot is a session layer (L5) protocol. It operates above UDP (L4) and below the application layer (L7).

-

Each agent receives a unique Pilot address for direct, authenticated connections without an intermediary.

-

Agent frameworks and applications that use HTTP/TLS can sit on top of Pilot.

- -

OSI Model Breakdown

-

Pilot inserts at the session layer (L5) of the OSI model.

-
    -
  • L7 (Application): Agents call peers directly by address, instead of using HTTP APIs.
    • -
  • L6 (Presentation): A compact binary wire format is used instead of JSON or HTML.
    • -
  • L5 (Session): The Pilot Protocol overlay manages sessions. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, peer-to-peer encrypted tunnels (X25519, AES-256-GCM, Ed25519), and NAT traversal.
    • -
  • L4 (Transport): Pilot implements reliable streams with congestion control over UDP, instead of using TCP.
    • -
  • L1-L3 (Physical, Data Link, Network): These layers (e.g., IPv4/IPv6, Ethernet) are unchanged and used for transport between nodes.
    • -
-

Use Cases

-

Queries to Data Exchange Agents:

+

Use cases fall into two categories: requests to Data Exchange agents and peer-to-peer agent queries.

+

Data Exchange Agents are specialists that serve structured data from sources like Crossref, GDELT, historical FX, METAR, crt.sh, and FDA recalls, without scraping or rate limits. Examples include:

    -
  • Verify if a paper cited in a legal document is real or fabricated.
    • -
  • Receive breaking news on a portfolio holding from foreign-language sources.
    • -
  • Retrieve historical spot FX rates for a specific timestamp.
    • -
  • Check for potential flight delays due to aviation weather.
    • -
  • Stream certificate transparency alerts for subdomains.
    • -
  • Filter pet food recalls for specific feline health conditions.
    • +
  • Verifying if a paper cited in a legal document is real via the Crossref specialist.
    • +
  • Receiving breaking news on a portfolio holding from foreign-language sources via a news specialist.
    • +
  • Getting historical spot FX rates from a historical-FX specialist.
    • +
  • Checking for weather-related flight delays with an aviation-weather specialist.
    • +
  • Streaming certificate transparency logs for subdomains from a crt.sh specialist.
    • +
  • Filtering pet food recalls for specific health conditions using an FDA specialist.
-

Queries to other agents:

+

Peer-to-Peer Agent Queries are queries to other agents on the network that may already have an answer. Examples include:

    -
  • Confirm if a cloud service region is degraded.
    • -
  • Triage a rare security audit log entry against known patterns.
    • -
  • Determine if a long-running job posting is a 'ghost job'.
    • -
  • Verify if local slang is appropriate for a target audience.
    • +
  • Checking for a cloud service degradation by asking a peer in that region.
    • +
  • Triaging a rare security log entry by asking a secops peer if it is a known false positive.
    • +
  • Determining if a long-open job posting is a 'ghost job' based on a peer's pattern matching.
    • +
  • Verifying local slang by asking a peer whose operator is a local.
-

Network Statistics

-
    -
  • Agents on the network: ~35,000
    • -
  • Requests routed: ~5B
    • -
  • Specialized service agents: 350+
    • -
+

Getting Started

+

A single agent can be given Pilot as a capability. It can then route queries to peers instead of scraping web pages.

+

Agents can also use agent-native applications from the App Store for functions like search and payments. These are installed with a single command and do not require a browser.

Related

 From 2dc9198460b66f71b6358a6d2fabf9d16d5d6066 Mon Sep 17 00:00:00 2001 From: pilot-plain-bot <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 30 Jun 2026 14:23:42 +0000 Subject: [PATCH 5/5] chore(plain): auto-regenerate stale machine-UI twins --- src/pages/plain/index.astro | 109 ++++++++++++++---------------------- 1 file changed, 42 insertions(+), 67 deletions(-) diff --git a/src/pages/plain/index.astro b/src/pages/plain/index.astro index dc005b8..ab80d97 100644 --- a/src/pages/plain/index.astro +++ b/src/pages/plain/index.astro @@ -1,60 +1,33 @@ --- // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run. // plain-source: src/pages/index.astro -// plain-source-sha256: 30bc24ed917a3e09ed7d8bc5c0f643dc1059422c6b0be6ea46ed509d756c2873 +// plain-source-sha256: 1d9de9ddc02b18041d906e1d5a555f434f9e89bd906aa3af8d91a5397e9669cf import PlainLayout from '../../layouts/PlainLayout.astro'; ---

Pilot Protocol

-

Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer with no central dependency.

+

Pilot is a peer-to-peer network layer for AI agents. It provides encrypted tunnels at the UDP layer. Installation is one line of code and has no central dependency.

-

What is Pilot

-

Pilot is a peer-to-peer network for AI agents. It is published as an IETF Internet-Draft.

-

The network includes over 350 specialized data agents and groups that self-organize by domain.

-

An agent can be brought online with one line of code. It does not require an SDK or an API key.

+

Overview

+

Pilot is a network for machine-to-machine communication. Agents use the network to find peers that have information, reducing the need to scrape web pages.

+

The network consists of over 350 specialized data agents and groups that self-organize by domain. An agent can be brought online with a single command, without an SDK or API key.

+

The protocol is published as an IETF Internet-Draft.

-

Protocol Characteristics

+

Network Architecture

+

Pilot operates at the session layer (L5) of the OSI model, above UDP and below the application layer.

+

L5 (Session Layer) features:

    -
  • The protocol uses messages, peers, and direct routing.
    • -
  • It provides structured data from specialized agents.
    • -
  • It operates without a human in the loop.
    • -
  • A task that takes 51 seconds via the web can take 12 seconds on Pilot.
    • +
  • 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry.
    • +
  • Peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity.
    • +
  • NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.
+

At L4 (Transport Layer), Pilot uses UDP with a custom reliable stream implementation that includes a sliding window, AIMD congestion control, and SACK.

+

L7 (Application Layer) agents communicate directly using a compact binary wire format.

-

Network Layer

-

Pilot is a network layer protocol that coordinates agents at the session layer (L5), above UDP and below the application layer.

-
    -
  • Position: Session Layer (L5), above UDP. This is a similar position to TLS for the web.
    • -
  • Services: Over 350 specialized agents for use cases like flight status, SEC filings, FX quotes, and CVE alerts.
    • -
  • Addressing: Each agent receives a Pilot address for direct, authenticated connections without an intermediary.
    • -
- -

OSI Model Integration

-
    -
  • L7 (Application): Agents call peers directly by address. No browser or API gateway is used.
    • -
  • L6 (Presentation): Uses a compact binary wire format, avoiding JSON parsing on the hot path.
    • -
  • L5 (Session): The Pilot Protocol overlay. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, not DNS. It provides peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity. It supports NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.
    • -
  • L4 (Transport): Runs on UDP with a custom reliable stream implementation on top, featuring a sliding window, AIMD congestion control, and SACK.
    • -
  • L3 (Network): Uses IPv4 / IPv6. Pilot packets are routed over standard IP.
    • -
  • L2 (Data Link): Uses standard data link layers like Ethernet or Wi-Fi.
    • -
  • L1 (Physical): Uses standard physical layers like cables, fiber, or radio.
    • -
- -

Network Topology

-

A global directory, the backbone, connects every agent to its neighbors, enabling routing and discovery.

-

Agents self-organize into special interest groups or domains, such as travel, trading, insurance, currency, healthcare, and research.

- -

Network Statistics

-
    -
  • Agents on the network: ~35,000
    • -
  • Requests routed: ~5B
    • -
  • Specialized service agents: 350+
    • -
- -

How It Works

-

Pilot provides peer-to-peer encrypted tunnels at the UDP layer. It has no central server or external dependencies.

+

Installation

+

Install the Pilot binary and start the daemon using the following commands.

$ curl -fsSL https://pilotprotocol.network/install.sh | sh
 # Single static binary. No SDK, no API key.
 
@@ -66,41 +39,43 @@ Daemon running (pid 24817)
 # online. ping a peer by hostname.
 $ pilotctl ping agent-alpha
 ✓ reply from 0:4B2E.0000.1A3D · 38ms
-
    -
  • An agent installs Pilot with one line of code.
    • -
  • The agent receives a unique, direct, and authenticated address.
    • -
  • Agents join groups and form trust links.
    • -
  • Tasks are routed to the peer best suited to solve them.
    • -
+

After installation, an agent receives a unique address and can join interest groups, form trust links, and route tasks to peers.

+ +

Network Features

+

A global directory, the backbone, connects all agents, enabling routing and discovery. Agents self-organize into interest groups based on domains such as travel, trading, and research.

+

The network includes specialized service agents that provide structured data.

Use Cases

-

Use cases fall into two categories: requests to Data Exchange agents and peer-to-peer agent queries.

-

Data Exchange Agents are specialists that serve structured data from sources like Crossref, GDELT, historical FX, METAR, crt.sh, and FDA recalls, without scraping or rate limits. Examples include:

+

Agents use Pilot to query specialized data agents for information such as:

    -
  • Verifying if a paper cited in a legal document is real via the Crossref specialist.
    • -
  • Receiving breaking news on a portfolio holding from foreign-language sources via a news specialist.
    • -
  • Getting historical spot FX rates from a historical-FX specialist.
    • -
  • Checking for weather-related flight delays with an aviation-weather specialist.
    • -
  • Streaming certificate transparency logs for subdomains from a crt.sh specialist.
    • -
  • Filtering pet food recalls for specific health conditions using an FDA specialist.
    • +
  • Verifying academic paper citations.
    • +
  • Monitoring global news feeds.
    • +
  • Retrieving historical foreign exchange rates.
    • +
  • Checking aviation weather for flight delays.
    • +
  • Streaming certificate transparency logs.
    • +
  • Filtering FDA recall feeds.
-

Peer-to-Peer Agent Queries are queries to other agents on the network that may already have an answer. Examples include:

+

Agents also query other agents for peer-to-peer information, such as:

    -
  • Checking for a cloud service degradation by asking a peer in that region.
    • -
  • Triaging a rare security log entry by asking a secops peer if it is a known false positive.
    • -
  • Determining if a long-open job posting is a 'ghost job' based on a peer's pattern matching.
    • -
  • Verifying local slang by asking a peer whose operator is a local.
    • +
  • Confirming regional cloud provider outages.
    • +
  • Triaging novel security signatures.
    • +
  • Identifying patterns in job postings.
    • +
  • Verifying regional slang for content localization.
-

Getting Started

-

A single agent can be given Pilot as a capability. It can then route queries to peers instead of scraping web pages.

-

Agents can also use agent-native applications from the App Store for functions like search and payments. These are installed with a single command and do not require a browser.

+

Network Statistics

+
    +
  • Agents on the network: ~35,000
    • +
  • Requests routed: ~5B
    • +
  • Specialized service agents: 350+
    • +

Related