pilot-service-agents-knowledge
Structured-knowledge and factual lookups — Google Knowledge Graph (premium), DuckDuckGo Instant, Archive.org, holidays, geocoders.
All agents in this category follow the standard contract described in
pilot-service-agents. Send /help to any agent to read its exact filter
schema — the table below is a snapshot; the catalogue grows, so always verify
with a fresh list-agents query.
Agents in this category (snapshot)
| Hostname | Description |
|---|---|
archive-org-search |
Internet Archive — 40M+ books, media, software |
duckduckgo-instant |
DuckDuckGo Instant Answers — factual topic lookups |
gcp-knowledge-graph |
Google Knowledge Graph entity search (100K/day free) |
mediawiki-random |
Random Wikipedia article summary |
nager-public-holidays |
Public holidays for 110+ countries |
photon-geocode |
Photon OpenStreetMap global geocoder |
universities-hipolabs |
Global university list by country |
wikipedia-search |
Wikipedia full-text search |
wikipedia-summary |
Wikipedia article summary by title |
wikiquote-search |
Wikiquote full-text search |
What you can expect
- Premium Google Knowledge Graph (hostname gcp-knowledge-graph) with linked entity IDs
- Free community sources for cross-validation
What NOT to expect
- Certifiably-cited truth — outputs are best-effort from upstream
Commands (same pattern for every agent in the category)
# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help" --wait
# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}' --wait
# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}' --wait
Response shape
With --wait, send-message blocks until the agent replies (up to 30 s by default) and prints one JSON document: the ACK fields ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}) plus reply, the agent's message. The agent's normalised envelope is the JSON string in data.reply.data (pilotctl v1.12.2 and older print two JSON documents instead: the send result, then the reply, whose data.data is the envelope). A non-zero exit means no reply arrived (the error JSON on stderr has a code such as timeout) — treat that as no data, never as a cue to read older messages from the inbox. A reply that lands after the wait can still be picked up by sender and time: pilotctl --json inbox --from <hostname> --since 5m --latest. The envelope:
{
"source": "<hostname>",
"items": [...],
"count": <int>,
"total": <int|null>,
"page": <int|null>,
"next": <cursor|null>,
"truncated": <bool>,
"upstream_url": "<resolved upstream URL>"
}
/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.
Workflow Example
# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"knowledge","limit":20}' --wait
# 2. Read the contract of a specific agent
pilotctl --json send-message nager-public-holidays --data '/help' --wait
# 3. Query it
pilotctl --json send-message nager-public-holidays --data '/data {"countryCode":"US","year":2026}' --wait
Dependencies
Requires the pilot-protocol core skill, the pilot-service-agents skill
(for the general discovery flow), pilotctl on PATH, and a running daemon
registered with the backbone (Network 0 — joined automatically at registration).