Install Jentic One Beta

Connect the BART Legacy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BART Legacy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.bart.gov%2Fbart" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.bart.gov%2Fbart" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BART Legacy API.

Get real-time estimated departures for a station

Retrieve station details and the list of stations

Look up route information for the system

Read schedules for trips and routes

Get current service advisories and delays

GET STARTED

Start building with BART Legacy API

Explore with Jentic One

View OpenAPI Document

★ Real-Time Departure Assistant

A commuting assistant reports the next trains leaving a station so a rider knows when to leave. It reads the estimated departures for the station and formats the times and destinations. Through Jentic the agent finds the departures operation and calls it with the station abbreviation.

Get the estimated departures for a station and report the next trains and their destinations

Trip Planning with Schedules

A trip-planning agent builds an itinerary using BART schedules and route information. It reads the routes and schedules to lay out connections and times. This lets a planner suggest departures that line up with a rider's target arrival.

Read the schedule and routes to plan a trip between two stations at a target time

Service Disruption Alerts

An alerting agent watches for BART service advisories and notifies riders of delays. It polls the advisories operation and surfaces any active disruption. Riders get a heads-up before they reach the platform.

Poll service advisories and notify a rider when a new disruption is active

Station Directory Lookup

A mapping agent lists BART stations and pulls details for one selected by a user. It reads the station list and then the details for a chosen station. This backs a picker or map overlay with authoritative station data.

List the BART stations and retrieve the details for a selected station

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for bart legacy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/etd.aspx

Get real-time estimated departures

GET

/stn.aspx

Get station information

GET

/sched.aspx

Get schedules

GET

/route.aspx

Get route information

GET

/bsa.aspx

Get service advisories

GET

/version.aspx

Get the API version

GET

/etd.aspx

Get real-time estimated departures

GET

/stn.aspx

Get station information

GET

/sched.aspx

Get schedules

GET

/route.aspx

Get route information

GET

/bsa.aspx

Get service advisories

GET

/version.aspx

Get the API version

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring BART by hand means managing its key query parameter against api.bart.gov and threading it through every departures and schedule call yourself. Through Jentic you install once, import BART from the API Directory, store the key once, and your agent calls it.

Permission scoping

BART is read-only, so a rule limits your agent to the operations it needs, such as departures and advisories. You choose which operations it may call, so schedules or routes are included only when you add them.

Credential isolation

Your BART API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get real-time departures' or 'check service advisories', and Jentic returns the matching BART operation with its parameters so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BART Legacy API through Jentic.

Why is there no official OpenAPI spec for BART Legacy API?

BART does not publish an OpenAPI specification for its legacy API. Jentic generates and maintains this spec so that AI agents and developers can call the BART Legacy API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the BART Legacy API use?

The BART Legacy API authenticates with an API key passed as the key query parameter. Through Jentic, that key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

Can I get real-time departures from the BART Legacy API?

Yes. The estimated departures operation returns the next trains leaving a station with their destinations and times. An agent can call it with a station abbreviation to report live departure information to a rider.

What are the rate limits for the BART Legacy API?

The OpenAPI spec does not specify rate limits for the BART Legacy API. Check the BART developer documentation at https://api.bart.gov/docs/overview/index.aspx for current limits, and back off when you receive a 429 response.

How do I get station departures through Jentic?

Search Jentic for 'get real-time departures', import BART from the API Directory, and store your key once. Jentic returns the departures operation with its station parameter so your agent can call it directly and read back the next trains.

Can I limit what my agent is allowed to do with the BART Legacy API?

Yes. The API is read-only, so you write a rule that allows the agent only the operations it needs, such as departures and advisories, leaving schedules or routes out unless you add them. Because Jentic One is self-hosted, those rules and the audit log of every call stay on your own infrastructure.

Is there a BART Legacy API MCP server?

You do not need an MCP server to give your agent the BART Legacy API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can read departures, schedules, and advisories. That also keeps your agent's context free of an extra server's tool definitions.

Bart Gov BART Legacy API

Name: BART Legacy API
Brand: BART API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMaps GeolocationRouting Directionsapikey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Retrieve BART real-time estimated departures, station and route information, schedules, and service advisories for the San Francisco Bay Area.

Use for: I want the next departures from a BART station, Get details for a specific station, List all BART stations, Look up the routes in the BART system

Not supported: Read-only BART transit data for the San Francisco Bay Area. Does not sell tickets, handle payments, or cover transit systems outside BART.

Jentic publishes the only available OpenAPI specification for BART Legacy API, keeping it validated and agent-ready. The BART Legacy API exposes real-time and scheduled transit data for the San Francisco Bay Area Rapid Transit system. It returns estimated departures for a station, station details and lists, route information, and schedules, along with current service advisories. Every operation is a read, so an agent can plan trips and report delays without changing anything on the service.

Jentic One on Github View OpenAPI Document