Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

SF Bay 511 (BYOK) — connector documentation

  • MCP endpoint: https://byok-sf-bay-511.connectorbay.com/mcp
  • REST API: POST https://byok-sf-bay-511.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sf-bay-511.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own SF Bay 511 API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-sf-bay-511.connectorbay.com/health · Tool schemas: https://byok-sf-bay-511.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-sf-bay-511 · agent@connectorbay.com

What SF Bay 511 (BYOK) is for

SF Bay 511 (BYOK) lets an AI assistant read your own SF Bay 511 data through the SF Bay 511 API with a key you supply (API key). Read-only: 12 tools (list_transit_operators, list_gtfs_feeds, list_transit_lines, list_transit_stops, get_line_timetable, list_transit_holidays, get_stop_arrivals, get_scheduled_departures, list_service_alerts, list_traffic_events, list_work_zones, list_toll_programs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.511.org. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SF Bay 511. SF Bay 511 and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which transit operators does 511 cover in the Bay Area?"
  • "Which Bay Area GTFS feeds are available and when were they last updated?"
  • "Which lines does Muni run?"
  • "Which stops does Muni line 38 serve?"
  • "What is the timetable of BART line COLS/OAKL?"
  • "Which holidays change Muni service?"

What it does

  • list_transit_operators: List the Bay Area transit operators (agencies): id, name, short name, primary mode, time zone, website and whether live data is monitored. Operator ids are used by the other transit tools.
  • list_gtfs_feeds: List the operators that publish a GTFS schedule feed through 511, with the time each feed was last generated. The id RG is the regional combined feed.
  • list_transit_lines: List the lines (routes) of one operator with id, name, transport mode and whether real-time data is monitored.
  • list_transit_stops: List the stops of one operator, optionally for one line, direction or pattern, with id, name, location, stop type, platform code and parent station. Large operators return a lot of data; narrow with the optional filters when offered.
  • get_line_timetable: Get the scheduled timetables of one line: day types, trips and passing times, optionally the holiday or special service for one exception date. Large operators return a lot of data; narrow with the optional filters when offered.
  • list_transit_holidays: List the service exception dates (holidays) of one operator with their start and end times; use them with get_line_timetable.
  • get_stop_arrivals: Get the live predicted arrivals and departures at one stop in SIRI format: line, direction, destination, expected and aimed times.
  • get_scheduled_departures: Get the scheduled departures at one stop for one operator, optionally for one line and a time window (SIRI stop timetable).
  • list_service_alerts: List the current transit service alerts (GTFS-realtime format) for one operator or the whole region: affected agency, cause, effect, active period and text.
  • list_traffic_events: List current Bay Area traffic events (incidents, road works, special events) from CHP and Caltrans: headline, type, severity, roads, lane status and location.
  • list_work_zones: List active Bay Area road work zones in the USDOT WZDx format: road names, direction, event dates, vehicle impact and description.
  • list_toll_programs: List the Bay Area toll programs with their toll signs, destinations and current toll prices (express lanes and bridges).

BYOK key

You bring your own SF Bay 511 API key (https://511.org/open-data/token). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.511.org over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Data provided by 511.org (Metropolitan Transportation Commission): show the credit 'powered by 511.org' with a link to 511.org wherever the data is displayed.

Data sources

Live from the SF Bay 511 API (api.511.org) with a BYOK key; documentation: https://511.org/open-data/transit. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SF Bay 511. SF Bay 511 and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your SF Bay 511 account.

Built for: Worldwide. Languages: English.