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.
15 methods · 27 MB download · category: browser · v0.20.0 · MIT.
+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.
+13 methods · 37 MB download · category: database · v17.5.0 · PostgreSQL.
Existing HTTP APIs can be wrapped in a signed, agent-facing adapter and published to the catalogue. There are two ways to publish.
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
+