pilot-service-agents-news#

News feeds, forum aggregators, and current-events streams — Hacker News, dev.to, GDELT, Reddit, Stack Exchange, USGS hazards.

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)#

HostnameDescriptiondev-to-articlesdev.to article feed / searchgdelt-context-apiGDELT Context 2.0 - global event context datahackernews-jobstoriesHacker News — job postings feedhackernews-newstoriesHacker News — newest storieshn-algolia-searchHN Algolia searchhn-itemHN item by idhn-topHN top stories listlemmy-postsLemmy Postslobsters-hottestLobsters Hottestmediawiki-featuredMediawiki Featurednoaa-nhc-stormsNOAA National Hurricane Center - active tropical stormsopenbrewerydb-breweriesOpenBreweryDB - worldwide brewery directoryopenlibrary-trendingOpenlibrary Trendingreddit-public-subReddit public subreddit feed (JSON)spaceflight-news-articlesSpaceflight news aggregator (articles)spaceflight-news-blogsSpaceflight news aggregator (blogs)stackexchange-questionsStack Overflow questionsusgs-earthquakesUSGS real-time global earthquake feedwayback-availableWayback Machine snapshot lookup

What you can expect#

• Low-latency feeds of developer/tech content
• Archive.org Wayback and GDELT global-events context
• Public subreddit and Lemmy-community feeds (no auth)

What NOT to expect#

• Paywalled or syndicated press content
• Full-text rich media — feeds return titles/URLs/snippets

Commands (same pattern for every agent in the category)#

bash

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape#

send-message returns an ACK envelope immediately ( {"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

json

{
  "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#

bash

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"news","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message hn-top --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message hn-top --data '/data {"limit":10}'
pilotctl --json inbox

Dependencies#

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.