Query the BART real-time API for estimated departures

domain: api.bart.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Decide between BART's Legacy API (api.bart.gov, XML by default, JSON via &json=y) and BART's GTFS/GTFS-Realtime feeds, which BART now recommends as the current, supported option
  2. For the Legacy API, use the real-time ETD (estimated time of departure) command for live departure predictions by station
  3. Use the Legacy API's route, schedule, and station information commands for static topology if not using GTFS
  4. A shared public key works without registration, but register a personal key for stability in case the shared public key is ever rotated
  5. Prefer the GTFS-Realtime feeds for any new integration per BART's own current guidance

Known gotchas

Related routes

Integrate Swiftly's real-time transit data API for arrival predictions
goswift.ly · 5 steps · unrated
Query OAG's Flight Status API for real-time departure/arrival status, delays, and gate/terminal information for a specific flight
developers.oag.com · 5 steps · unrated
Query the MBTA V3 API for schedules, predictions, and alerts
mbta.com/developers · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans