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

Transit (BYOK) — connector documentation

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

What Transit (BYOK) is for

Transit (BYOK) lets an AI assistant read your own Transit data through the Transit API with a key you supply (Transit API key). Read-only: 12 tools (list_available_networks, search_stops, list_nearby_stops, get_stop_details, list_nearby_routes, get_stop_departures, get_route_details, list_vehicles, list_service_alerts, get_network_latest_update, plan_trip, list_nearby_shared_vehicles). 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 external.transitapp.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Transit. Transit 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 networks does Transit cover in Canada?"
  • "Find the transit stop named 'Berri' near downtown Montreal."
  • "What transit stops are within 300 metres of 45.5231, -73.5964?"
  • "Tell me about transit stop STM:88368."
  • "Which bus and metro routes serve 45.5231, -73.5964 and when is the next departure?"
  • "When are the next buses at transit stop STM:88368?"

What it does

  • list_available_networks: List the transit networks (agencies and shared-mobility systems) Transit covers, optionally only those serving a point or a country, with their ids, region, type and modes. Map geometry is left out.
  • search_stops: Search transit stops by name or stop code near an approximate location; returns the best matches with ids and coordinates.
  • list_nearby_stops: List transit stops around a location with distance, code, coordinates, mode and wheelchair boarding info.
  • get_stop_details: Get one transit stop: name, code, coordinates, timezone, city, network and wheelchair boarding.
  • list_nearby_routes: List transit routes serving a location with their mode, network and the next departures of each direction.
  • get_stop_departures: Get upcoming departures at one or more stops for every route that serves them, with live times where the agency provides them.
  • get_route_details: Get one route with its directions, headsigns and ordered stop lists (no map shapes).
  • list_vehicles: Get live vehicle positions (coordinates, occupancy, wheelchair access, last update) for a route, where the agency publishes them.
  • list_service_alerts: List service alerts (detours, disruptions, closures) for one or more transit networks, with cause, effect, severity, active periods and affected routes and stops.
  • get_network_latest_update: Get the time of the most recent schedule data update Transit has for a network.
  • plan_trip: Plan a public transit trip between two coordinates or stops and return the best few options with duration, start and end times, fare and legs.
  • list_nearby_shared_vehicles: List shared bikes, e-bikes, scooters and docking stations around a location with network, availability text and coordinates.

BYOK key

You bring your own Transit Transit API key (https://transitapp.com/partners/apis). 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 external.transitapp.com 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.

Data sources

Live from the Transit API (external.transitapp.com) with a BYOK key; documentation: https://api-doc.transitapp.com/v4.html. 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 Transit. Transit 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 Transit account.

Built for: Worldwide. Languages: English.