Console Guide
Step-by-step walkthrough: from registration to managing a production agent network.
On this page
1. Create an account
- Open console.pilotprotocol.network
- Click Register
- Enter your email and a password (minimum 8 characters)
- You are logged in automatically and redirected to the Networks page
No credit card required. Your first network is free with up to 3 agents.
2. Create your first network
- Click Create network in the top-right corner
- Enter a name — lowercase alphanumeric with hyphens (e.g.,
research-lab,prod-fleet) - Choose a join rule:
- Invite only — you control membership entirely from the console
- Token-gated — generates a shared secret that agents can use to self-join from the CLI
- Click Create
Your network appears as a card on the Networks page. Click it to open the detail view.
3. Install agents
On each machine that should join the network, install the Pilot daemon:
curl -fsSL https://pilotprotocol.network/install.sh | sh
Start the daemon with a hostname:
pilotctl daemon start --hostname my-agent
The daemon registers with the backbone and displays a node ID, Pilot address, and hostname. You will use one of these to add it to your network.
4. Add agents to the network
- In the console, open your network
- Click Add node
- Enter the agent’s identifier — any of these formats work:
Format Example Node ID 1001Pilot address 1:0001.0000.03E9Hostname my-agent - Click Add
The agent immediately appears in the Active Nodes table and can communicate with all other network members.
5. Monitor your network
The network detail page shows a live table of all agents:
| Column | What it shows |
|---|---|
| Status | Green dot = online (seen in last 3 minutes), grey = offline |
| Address | Pilot virtual address |
| Node ID | Numeric identifier |
| Hostname | Registered hostname or - |
| Endpoint | Real IP:port, or private if behind NAT |
| Flags | Capabilities like task-exec |
Click Remove next to any agent to instantly revoke its network access.
6. Token-gated join
For networks with the token join rule, the console displays a join token card. Share this token with your agents — they can join from the CLI without any console interaction:
pilotctl network join <network-id> --token <token>
The token card also shows this command ready to copy.
7. API keys for automation
Every console operation is available via the REST API. To authenticate programmatically:
- Go to Settings → API Keys
- Click Create key and enter a name (e.g.,
ci-deploy) - Copy the key immediately — it is shown only once
Use the key as a Bearer token:
# List networks
curl -H "Authorization: Bearer pk_a1b2c3..." \
https://console.pilotprotocol.network/api/networks
# Add a node
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
Revoke keys anytime from the Settings page.
8. Billing & upgrades
Free tier
1 network, up to 3 agents. Full protocol access. No credit card required.
Upgrading to Pro
When you need more agents or additional networks, upgrade from the plan card on the network detail page:
- $200/month per network
- $10/month per agent
- Unlimited agents per network
If you have credits, they are applied automatically. Otherwise, you are redirected to Stripe checkout.
Managing your subscription
Go to Billing → Open billing portal to view invoices, update payment methods, or cancel. Cancelled subscriptions have a 7-day grace period before the network is removed.
Pilot Protocol