Integrations·Tools & Utilities
Bart + OpenClaw
Give your autonomous agents a live connection to Bart: managed, secure, and ready in minutes.
Bart is the Bay Area Rapid Transit system, providing fast public transportation across the San Francisco Bay Area. On Molted, your OpenClaw agents connect to Bart through the managed MCP integration layer, with no glue code, no servers to run, and no credentials baked into containers. The agent can automate tasks and connect this tool to the rest of your stack for Bart, autonomously and within the guardrails you set.
Available actions
10 ready-to-use Bart actions.
Your OpenClaw agents can call any of these Bart actions directly through Molted's managed MCP layer. No wrappers, no boilerplate.
BART_BART_GET_API_VERSION
Get BART API Version
Stub action for bart api version retrieval.
BART_BART_GET_AVAILABLE_SCHEDULES
Get BART Available Schedules
Tool to retrieve a list of currently released bart schedules. use when you need schedule versioning info.
BART_BART_GET_ROUTE_INFO
Get Route Info
Tool to fetch detailed information about a specific bart route. use when you know the route number (1–12) or need all routes configuration. call after…
BART_BART_GET_STATIONS
Get BART Stations
Stub action for bart stations retrieval.
BART_GET_GTFS_RT_TRIP_UPDATES
Get GTFS-RT Trip Updates
Tool to fetch real-time trip updates in gtfs-realtime format. use when you need the latest live trip information as raw protobuf.
BART_GET_GTFS_STATIC_SCHEDULE_FEED
Download GTFS Static Schedule Feed
Tool to download the static gtfs feed (google transit.zip). use when needing the latest gtfs schedule data.
BART_GET_SCHEDULE_ARRIVE
Get BART Schedule Arrive
Tool to retrieve schedule information based on a specified arrival time. use when planning trips arriving by a given time.
BART_GET_SCHEDULE_DEPART
Get BART Schedule Depart
Tool to get schedule information based on a specified depart time. use when planning trips from an origin to a destination with time constraints after…
BART_GET_SERVICE_ADVISORIES
Get Service Advisories
Tool to fetch current bart service advisories. use when you need up-to-date system-wide or station-level alerts before presenting or planning transit routes.
BART_GET_STATION_INFO
Get Station Info
Tool to fetch detailed information for a specified bart station. use after you have a station's abbreviation. (e.g., get station info for 'balb')
How the connection works
Connect once. The agent acts.
Bart connects with an API key you provide once; it is encrypted at rest and never shipped inside the agent's pod. Everything runs through Molted's managed MCP layer, so there is no integration code to write and nothing to keep running.
01
The agent requests access
Your OpenClaw agent asks for Bart when a task needs it.
02
You approve the connection
Authorize Bart once (API key). Credentials are encrypted at rest and scoped to what you allow.
03
The agent acts
It reads and writes to Bart autonomously, inside your guardrails, with full audit and revocable access.
FAQ
Bart on Molted, answered.
Q.01
Can OpenClaw agents use Bart on Molted?
Yes. Bart is one of 1,000+ apps available through Molted's managed MCP integration layer. Your agent requests access, you approve the connection, and it can act on Bart straight away, with no integration code to write or maintain.
Q.02
How do I connect Bart to my agent?
Bart connects with an API key you provide once; it is encrypted at rest and never shipped inside the agent's pod.
Q.03
What can an agent actually do with Bart?
Within the permissions you grant, an agent can automate tasks and connect this tool to the rest of your stack. With Bart, your agent can trigger actions in response to events from your other tools.
Q.04
Is my Bart data and credentials secure?
Yes. Molted never bakes credentials into the agent's pod: every connection is brokered through the managed integration layer, secrets are encrypted at rest, and access stays scoped to what you approve. You can revoke Bart access at any time.
Q.05
Do I have to run any infrastructure to use Bart?
No. Molted is the managed operating environment for autonomous agents: compute, the MCP layer, browser automation and self-healing are all handled for you. Connecting Bart is a configuration step, not an engineering project.
Q.06
Will the Bart connection stay live for an always-on agent?
Yes. Molted keeps Bart connections healthy for long-running agents, refreshing tokens and surfacing any re-auth, so autonomous workflows that depend on Bart keep running.
More Tools & Utilities integrations
Browse all 1,000+ integrations →
Ship agents that use Bart, not infrastructure.
Get an agent-ready environment, the managed MCP layer with 1,000+ integrations, and direct access to our engineers. Onboarding within days.