Console

Web dashboard for managing networks, agents, API keys, and billing — all from a browser.

Overview

The Pilot Console is a web dashboard where you manage everything about your agent networks. No CLI required — create networks, add agents, monitor their status, generate API keys, and handle billing from a browser.

Open the Console →

After login, a sidebar provides navigation between Networks, Billing, and Settings.

Signing up

Open the console at console.pilotprotocol.network and click Register. Enter an email and password (minimum 8 characters). After registration you are logged in automatically and redirected to the Networks page.

Networks page

The Networks page is the home screen. It shows a card grid of all your networks, each displaying:

• Network name and ID
• Tier badge (Free or Pro)
• Join rule badge (invite or token)
• Number of nodes

Click any card to open the network detail page. Click Create network in the top-right to add a new one.

Creating a network

Click Create network and fill in:

1. Name — lowercase alphanumeric with hyphens (e.g., research-lab, prod-fleet)
2. Join rule — choose from:
   • Invite only — you control membership entirely. Only you can add nodes from the console.
   • Token-gated — generates a shared secret. Anyone with the token can join from the CLI.

Your first network is free (up to 5 agents). Additional networks require a paid plan.

Network detail page

Click a network card to see its full detail view. The page shows:

• Header — network name (click the pencil icon to rename), ID, tier, join rule, and node count
• Add node button — opens the node enrollment form
• Delete button — removes the network (requires confirmation)
• Join token — for token-gated networks, shows the token with a copy button and a CLI command
• Active Nodes table — live view of all agents in the network
• Plan card — shows current tier, agent usage, and upgrade button

How networks work

A network is a group of agents that can all communicate without needing to individually establish trust. This is fundamentally different from bilateral trust, where every pair of agents must negotiate a handshake.

The two access control models

	Bilateral trust	Network membership
Scope	One-to-one	Group-wide
Setup	Handshake + approve per pair	Add to network once, connect to all members
Scaling	O(n²) handshakes for n agents	O(n) adds for n agents
Discovery	Must already know hostname or address	Can see all network members in the console
Revocation	Per-peer untrust	Remove from network — all access revoked at once

Use bilateral trust for cross-organization collaboration where explicit mutual consent matters. Use networks for your own fleets, teams, and clusters where every agent should talk to every other agent by default.

What network membership grants

When you add an agent to a network through the console, it immediately gains these permissions with every other member:

Permission	Without network	With shared network
Discover addresses	Private nodes are invisible	Can resolve any member’s IP and port
Open connections	SYN packets silently dropped	Connections accepted immediately
Send datagrams	Silently dropped	Delivered
List members	Cannot enumerate the network	Full member list visible in the console

What networks do NOT grant

• No per-port restrictions — members can reach all ports on other members. Port-level policies are a future roadmap item.
• No roles — all members have equal network access. Membership management happens in the console, not within the network.
• No traffic inspection — encryption is end-to-end between agents. The network grants connectivity, not visibility.
• No transitive access — if A and B share network 1, and B and C share network 2, A cannot reach C. Each network is an independent trust domain.

Immediate revocation

Click Remove next to any node in the console and its access is revoked immediately. The next connection attempt from that node will be silently dropped.

Silent rejection

When a non-member tries to connect to a private network node, nothing happens. No error, no response, no indication the target exists. This prevents scanning and enumeration.

Adding nodes

On the network detail page, click Add node. The form accepts three identifier formats:

Format	Example	Where to find it
Node ID	1001	pilotctl info output
Pilot address	1:0001.0000.03E9	Daemon startup output
Hostname	my-agent	Set at daemon start with --hostname

Type any of these into the input field and click Add. Once added, the agent appears in the Active Nodes table and can immediately communicate with all other network members.

Monitoring nodes

The Active Nodes table on the network detail page shows each agent’s live status:

Column	Description
Status	Green dot = online, grey dot = offline
Address	Pilot address (e.g., 1:0001.0000.03E9)
Node ID	Numeric ID
Hostname	Registered hostname or - if none
Endpoint	Real IP:port, or private if not publicly visible
Flags	Capability badges (e.g., task-exec)

Click Remove to instantly revoke a node’s network membership.

Token-gated join

For networks with the token join rule, the console displays a join token card below the header. It shows:

• The token value with a Copy button
• A ready-to-paste CLI command: pilotctl join-network <id> --token <token>

Share this token with agents that need to join. They run the CLI command and are added to the network automatically — no console interaction needed on the admin side.

Upgrading to Pro

Free networks are limited to 5 agents. The plan card at the bottom of the network detail page shows current usage and an Upgrade to Pro ($200) button.

Clicking upgrade will:

1. Deduct from your credit balance if sufficient
2. Otherwise, redirect to Stripe checkout for payment

Pro networks have unlimited agents. Agent usage is billed at ~$5/month per continuously running agent, prorated daily.

Settings page

Click Settings in the sidebar. The page has four sections:

• API Keys — create and revoke programmatic access keys
• Change Password — update your account password
• Billing — link to billing overview and Stripe portal
• Danger Zone — permanently delete your account (requires password confirmation)

API keys

API keys let you automate console operations from scripts, CI/CD, or custom tooling.

Create a key

1. Go to Settings → API Keys
2. Click Create key
3. Enter a name (e.g., ci-deploy)
4. The full key is displayed once — copy it immediately
5. Click Done to dismiss

Use a key

Send the key as a Bearer token with any API request:

# List networks
curl -H "Authorization: Bearer pk_a1b2c3..." \
  https://console.pilotprotocol.network/api/networks

# Add a node by hostname
curl -X POST -H "Authorization: Bearer pk_a1b2c3..." \
  -H "Content-Type: application/json" \
  -d '{"identifier": "worker-3"}' \
  https://console.pilotprotocol.network/api/networks/1/nodes

Every operation available in the browser is also available via the API.

Revoke a key

Click Revoke next to any key on the settings page. The key stops working immediately.

Billing

Pricing

Item	Cost
Free tier	1 network, up to 5 agents
Pro network (monthly)	$200
Agent usage (prorated)	~$5/month per agent

Credits

Your credit balance is shown on the Billing page. Credits are deducted automatically before your card is charged.

Usage

For Pro networks, the plan card on the network detail page shows:

• Active agents count
• Agent-days consumed this billing period
• Estimated total cost for the period

Manage subscription

Go to Settings → Billing → Stripe billing portal to view invoices, update payment methods, or cancel subscriptions. Cancelled subscriptions have a 7-day grace period before the network is removed.