Understand the
network layer.
Short paths through the decisions that matter when agents need to find and reach one another across machines, clouds, and organizations.
These guides keep four questions separate: Can the peers connect? Who is connecting? What may the application do? What evidence remains?
Start with the question
in front of you.
What does Pilot provide?
Map addresses, tunnels, discovery, trust, apps, and application authority to the right layers.
Start here →02 · TransportWhich messaging stack fits?
Compare request/response, brokers, persistent paths, and overlays without treating them as interchangeable.
Compare options →03 · SecurityWhich credential proves what?
Separate daemon identity and tunnel admission from API authorization, roles, data access, and approval.
Review identity →Eight focused
technical guides.
Foundations
What Is Pilot Protocol?
A system-level introduction to persistent agent addresses, encrypted peer tunnels, discovery, trust, and installable capabilities.
What Makes a Pilot Agent?
The identity, daemon, address, trust relationship, and application boundary that turn an existing agent into a network participant.
AI Networking Across Multiple Clouds
How agent connectivity changes when workloads span cloud accounts, edge devices, laptops, and organizational boundaries.
Transport
gRPC and UDP Transport Options
A precise look at gRPC transport assumptions, UDP overlays, and where each layer belongs in an agent communication stack.
NATS vs. gRPC for Agent Messaging
Compare connectivity models, messaging patterns, deployment requirements, and the role of an overlay beneath either option.
MCP Tunnels vs. VPNs for Agents
Separate tool access, network reachability, identity, and authorization so similarly named approaches are evaluated on the right boundary.
Security
How Network Agent Tokens Differ
Compare an agent cryptographic identity with API keys, bearer tokens, and application-level credentials without collapsing the layers.
How X25519 Secures Agent Communication
Understand key agreement, tunnel secrets, authenticated encryption, and the limits of what transport cryptography can authorize.
Connectivity is only
one decision.
An authenticated tunnel proves which daemon is on the other end and protects traffic in transit. It does not, by itself, approve a purchase, release protected data, or let an agent bind an organization.
Use the Trust Center for implemented security boundaries, Governance for the shared-responsibility model, and Documentation for version-specific commands.