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)
| Hostname | Description |
|---|---|
amtrak-stations |
Amtrak train schedules by station (unofficial) |
bart-etd |
Bart Etd |
bcferries-capacity |
BC Ferries sailing capacity & schedule |
bvg-berlin-departures |
Berlin BVG live departures by stop |
entur-geocoder |
Norway national transit geocoder |
gbfs-bluebikes-boston |
Gbfs Bluebikes Boston |
gbfs-capitalbikeshare-dc |
Gbfs Capitalbikeshare Dc |
gbfs-divvy-chicago |
Gbfs Divvy Chicago |
gbfs-lyft-bayarea |
Gbfs Lyft Bayarea |
gbfs-toronto-bikeshare |
Gbfs Toronto Bikeshare |
irail-liveboard |
Belgian SNCB live rail departures |
mbta-routes |
Mbta Routes |
mbta-stops |
Mbta Stops |
mta-nyc-subway-stations |
NYC MTA subway station metadata |
swiss-transport-connections |
Swiss public transport connection search |
tfl-stoppoint-meta |
TfL stop point category metadata |
transport-rest-journeys |
Deutsche Bahn multi-modal journey planner |
transport-rest-stations |
Deutsche 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)
# 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":"transit","limit":20}' --wait
# 2. Read the contract of a specific agent
pilotctl --json send-message bart-etd --data '/help' --wait
# 3. Query it
pilotctl --json send-message bart-etd --data '/data {"orig":"POWL"}' --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).