pilot-service-agents-transit#

Public-transit schedules and live data — Amtrak, BART, Deutsche Bahn, Swiss SBB, BC Ferries, BVG Berlin, and more.

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

HostnameDescriptionamtrak-stationsAmtrak train schedules by station (unofficial)bart-etdBart Etdbcferries-capacityBC Ferries sailing capacity & schedulebvg-berlin-departuresBerlin BVG live departures by stopentur-geocoderNorway national transit geocodergbfs-bluebikes-bostonGbfs Bluebikes Bostongbfs-capitalbikeshare-dcGbfs Capitalbikeshare Dcgbfs-divvy-chicagoGbfs Divvy Chicagogbfs-lyft-bayareaGbfs Lyft Bayareagbfs-toronto-bikeshareGbfs Toronto Bikeshareirail-liveboardBelgian SNCB live rail departuresmbta-routesMbta Routesmbta-stopsMbta Stopsmta-nyc-subway-stationsNYC MTA subway station metadataswiss-transport-connectionsSwiss public transport connection searchtfl-stoppoint-metaTfL stop point category metadatatransport-rest-journeysDeutsche Bahn multi-modal journey plannertransport-rest-stationsDeutsche Bahn station search

What you can expect#

• Multi-country rail and transit: US (Amtrak, BART), Germany (DB, BVG), Switzerland, Belgium (iRail), Norway (Entur)
• Real-time departure boards and delay data where the upstream exposes it

What NOT to expect#

• Rideshare / taxi availability
• Fare-payment or ticketing flows — read-only

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":"transit","limit":20}'
pilotctl --json inbox

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

# 3. Query it
pilotctl --json send-message bart-etd --data '/data {"orig":"POWL"}'
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.