TransitFeeds API
71
AI ReadinessAI-Aware (A-)71/100
Maps GeolocationGeocodingnone4 EndpointsREST
For Agents
Programmatically retrieve a list of versions of specified (or all) feeds., retrieve a list of feeds.. Covers 4 operations.
Use for: I need to a list of versions of specified (or all) feeds., I want to a list of feeds., Search for the download url for the latest version of a feed., Find all a list of locations.
Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.
API to view feed information and download feeds from TransitFeeds.com. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the TransitFeeds API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TransitFeeds 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.
1
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%2Ftransitfeeds.com%2Ftransitfeeds" | sh2
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%2Ftransitfeeds.com%2Ftransitfeeds" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 TransitFeeds API.
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
Patterns agents use TransitFeeds API for, with concrete tasks.
★ 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..
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.
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.
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
4 endpoints — api to view feed information and download feeds from transitfeeds.
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.
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.
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
TransitFeeds API
- AI-Aware (A-)71/100
74
Foundational Compliance58
Developer Experience & Jentic Compatibility58
AI-Readiness & Agent Experience94
Agent Usability100
Security72
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
31%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
58
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
83%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
72
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
72%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using TransitFeeds API through Jentic.
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.
GET STARTED