canonical: https://jentic.com/apis/sfbay511.org/sfbay511

# Sfbay511 511 SF Bay Transit API

API providing San Francisco Bay Area transit data including real-time vehicle positions, trip updates, service alerts, stop monitoring, and schedule information. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get list of gtfs transit operators, get gtfs data feed for an operator. Covers 15 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Get list of GTFS transit operators
- Manage productivity data programmatically
- Integrate 511 SF Bay Transit API into automated workflows
- Query and filter 511 SF Bay Transit API records by parameters
- Monitor 511 SF Bay Transit API operational status and events

## Use cases

### Productivity Operations

Use the 511 SF Bay Transit API to perform productivity operations programmatically. The API provides 15 endpoints covering core functionality including get list of gtfs transit operators, get gtfs data feed for an operator, get real-time trip updates for an agency.

Example prompt: Call GET /transit/gtfsoperators to get list of gtfs transit operators

### Automated DataFeeds Management

Automate datafeeds operations by combining multiple 511 SF Bay Transit API endpoints. Agents can get gtfs data feed for an operator and then get real-time trip updates for an agency in a single workflow.

Example prompt: Call GET /transit/datafeeds to get gtfs data feed for an operator, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call 511 SF Bay Transit API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get list of gtfs transit operators', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /transit/gtfsoperators | Get list of GTFS transit operators |
| GET | /transit/datafeeds | Get GTFS data feed for an operator |
| GET | /transit/tripupdates | Get real-time trip updates for an agency |
| GET | /transit/vehiclepositions | Get real-time vehicle positions for an agency |
| GET | /transit/servicealerts | Get service alerts |
| GET | /transit/StopMonitoring | Get real-time stop monitoring data |
| GET | /transit/VehicleMonitoring | Get real-time vehicle monitoring data |
| GET | /transit/operators | Get transit operators |

## Key resources

- **DataFeeds** — Bulk GTFS data feeds
- **RealTime** — Real-time transit data
- **Schedule** — Transit schedule and stop information

## Why Jentic

- **Setup:** Wiring the 511 SF Bay Transit API by hand means appending your api_key query parameter to every transit request and parsing the GTFS and monitoring feeds yourself. Through Jentic you install once, import the 511 SF Bay Transit API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The 511 SF Bay Transit API passes the api_key as a query parameter and exposes read-only transit feeds, so limit the agent to the operations it needs, such as listing operators or reading vehicle positions. You choose the operations it may call, so it holds only that read access.
- **Credential handling:** Your 511 SF Bay Transit 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.
- **Discovery method:** Agents search Jentic by intent such as 'list GTFS transit operators' or 'get real-time vehicle positions', and Jentic returns the matching 511 SF Bay Transit API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the 511 SF Bay Transit API use?

The 511 SF Bay Transit API uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get list of gtfs transit operators with the 511 SF Bay Transit API?

Yes. Use the GET /transit/gtfsoperators endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the 511 SF Bay Transit API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get list of gtfs transit operators through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get list of gtfs transit operators'. Jentic returns the matching 511 SF Bay Transit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the 511 SF Bay Transit API have?

The 511 SF Bay Transit API exposes 15 endpoints covering datafeeds, realtime, schedule operations.

### Can I limit what my agent is allowed to do with the 511 SF Bay Transit API?

Yes. Jentic One runs self-hosted on your own infrastructure, and your own rules decide which of the 511 SF Bay Transit API operations and which credentials your agent may use. Because these are read-only transit feeds, you can restrict the agent to only the endpoints it needs, such as GET /transit/gtfsoperators to list operators or GET /transit/vehiclepositions to read real-time vehicle positions, while withholding others like trip updates or service alerts. The api_key is held once by your own instance and injected at execution time, so the agent gets only the read access you granted.