canonical: https://jentic.com/apis/transitfeeds.com/transitfeeds

# TransitFeeds API

API to view feed information and download feeds from TransitFeeds.com. The API exposes 4 endpoints.

## For AI agents

Programmatically retrieve a list of versions of specified (or all) feeds., retrieve a list of feeds.. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Retrieve a list of versions of specified (or all) feeds.
- Manage maps geolocation data programmatically
- Integrate TransitFeeds API into automated workflows
- Query and filter TransitFeeds API records by parameters
- Monitor TransitFeeds API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the TransitFeeds API to perform maps geolocation operations programmatically. The API provides 4 endpoints covering core functionality including retrieve a list of versions of specified (or all) feeds., retrieve a list of feeds., retrieve the download url for the latest version of a feed..

Example prompt: Call GET /getFeedVersions to retrieve a list of versions of specified (or all) feeds.

### Automated Getfeedversions Management

Automate getfeedversions operations by combining multiple TransitFeeds API endpoints. Agents can retrieve a list of feeds. and then retrieve the download url for the latest version of a feed. in a single workflow.

Example prompt: Call GET /getFeeds to retrieve a list of feeds., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TransitFeeds 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 none tokens manually.

Example prompt: Search Jentic for 'retrieve a list of versions of specified (or all) feeds.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /getFeedVersions | Retrieve a list of versions of specified (or all) feeds. |
| GET | /getFeeds | Retrieve a list of feeds. |
| GET | /getLatestFeedVersion | Retrieve the download URL for the latest version of a feed. |
| GET | /getLocations | Retrieve a list of locations. |

## Key resources

- **Getfeedversions** — Operations for getFeedVersions
- **Getfeeds** — Operations for getFeeds
- **Getlatestfeedversion** — Operations for getLatestFeedVersion
- **Getlocations** — Operations for getLocations

## Why Jentic

- **Setup:** Wiring the TransitFeeds API by hand still means coding against api.transitfeeds.com and handling its error responses yourself even though the endpoints are open. Through Jentic you install once, import the TransitFeeds API from the API Directory, and your agent calls it.
- **Permission scoping:** The TransitFeeds API is read-only, with feed and location selectors passed as query parameters rather than owned resource ids in the URL path, so scope the agent to the operations it needs, such as listing feeds or getting feed versions, and leave out anything the workflow does not require. Every operation you allow is one you have chosen.
- **Credential handling:** The TransitFeeds API endpoints in this spec require no credential, so there is nothing for your agent to hold; Jentic still injects any per-request configuration at execution time rather than placing it in the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available transit feeds' or 'get the latest feed version', and Jentic returns the matching TransitFeeds API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the TransitFeeds API use?

The TransitFeeds API uses no authentication. 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 retrieve a list of versions of specified (or all) feeds. with the TransitFeeds API?

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

### What are the rate limits for the TransitFeeds 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 retrieve a list of versions of specified (or all) feeds. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a list of versions of specified (or all) feeds.'. Jentic returns the matching TransitFeeds API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TransitFeeds API have?

The TransitFeeds API exposes 4 endpoints covering getfeedversions, getfeeds, getlatestfeedversion operations.

### Can I limit what my agent is allowed to do with the TransitFeeds API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which TransitFeeds operations and configuration your agent may use. The TransitFeeds API is read-only, so you can allow just the calls a workflow needs, such as GET /getFeeds to list feeds or GET /getFeedVersions to list versions, and leave out GET /getLatestFeedVersion or GET /getLocations if they are not required. Feed and location selectors are passed as query parameters, so every operation the agent can reach is one you have explicitly permitted.