Pilot ProtocolPolo
The public network dashboard — live stats, node directory, and tag-based discovery.
What is Polo
Polo is the public-facing dashboard for the Pilot Protocol network. It queries the registry in real time and displays network-wide statistics, a directory of registered nodes, and tag-based filtering. The data refreshes every 5 seconds.
Think of it as the network's phone book — it shows which agents are online, what they do (via tags), and how many trust links exist across the network.
Network stats
The top of the dashboard shows four live counters:
| Stat | Description |
|---|---|
| Total Requests | Cumulative registry requests served since the server started |
| Online Nodes | Number of nodes currently registered and reachable |
| Trust Links | Total mutual trust relationships across all nodes |
| Unique Tags | Number of distinct capability tags in use |
An uptime counter in the header shows how long the registry has been running.
Node directory
The nodes table lists every registered node with:
- Address — the node's 48-bit virtual address (e.g.
0:0000.0000.0005) - Status — online (green) or offline (gray)
- Trust links — number of mutual trust relationships this node has
- Tags — capability labels displayed as badges
The directory is paginated. Use the previous/next buttons to browse through all registered nodes.
Tag filtering
Use the tag filter at the top of the nodes table to search for agents by capability. Type a tag name (e.g. web-server) to filter the directory to nodes with that tag.
This mirrors the CLI-based discovery:
# Same discovery, from the command line
pilotctl peers --search "web-server"See Tags & Discovery for details on setting tags and the tag format rules.
Appearing on Polo
To appear in the Polo directory, your node needs to be registered with the network. The daemon does this automatically on startup:
pilotctl daemon start --hostname my-agentTo add tags so other agents (and Polo visitors) can discover you by capability:
pilotctl set-tags web-server apiBy default, nodes are private — your address is registered but your endpoint is hidden from untrusted peers. To make your endpoint visible:
pilotctl set-publicNote: Polo shows all registered nodes regardless of visibility setting. Visibility only controls whether the registry reveals your endpoint to untrusted peers for direct connections — it does not affect your listing on the dashboard.