Bart for AI agents
BART's API provides real-time Bay Area Rapid Transit data, including train departures, service alerts, fares, and station information, used by apps that help riders plan trips. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Bart.
Check next train departures
Get estimated departures for a station so a rider knows when the next train actually arrives.
Check for service alerts
Get current service advisories and elevator status for a station before telling a rider to expect delays.
Look up a fare between stations
Get the fare between two stations to answer a rider's question, a read-only lookup with no booking involved.
20 Bart actions, graded by risk.
Every Bart action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
20Look things up. Allowed by default.
- bart.get_fareGet BART Fare
- bart.list_routesList BART Routes
- bart.get_stationsGet BART Stations
- bart.get_route_infoGet Route Info
- bart.get_api_versionGet BART API Version
- bart.get_gtfs_alertsGet GTFS-RT Service Alerts
- bart.get_train_countGet Train Count
- bart.get_station_infoGet Station Info
- bart.get_route_scheduleGet Route Schedule
- bart.get_station_accessGet Station Access
- bart.get_elevator_statusGet Elevator Status
- bart.get_schedule_arriveGet BART Schedule Arrive
- bart.get_schedule_departGet BART Schedule Depart
- bart.get_station_scheduleGet Station Schedule
- bart.get_special_schedulesGet Special Schedules
- bart.get_service_advisoriesGet Service Advisories
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Bart in three steps.
- 01Your users connect BartThey add their Bart api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Bart through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bart', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bart connects.
Users add their Bart api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Bart connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Bart from any agent.
Bart and Arc0, answered.
Can I use Bart with Claude, ChatGPT or Cursor?
Yes. Connect Bart to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Bart actions you allow.
How do users connect Bart?
Users add their Bart api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Bart actions can my agent take?
20 in total: 20 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Bart?
Yes. Allow read actions and deny writes in the Bart policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Bart too?
Yes. The same Bart connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bart into your agent.
Your users connect Bart once, under your brand. Your agent gets 20 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan