Transit
Providers using this tag (31)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 1 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 6 Almost no public developer surface
APIs with this tag (13)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 1 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
CTA Customer Alerts APIThe Customer Alerts API delivers real-time service status, planned outages, and disruption information for ...CTA GTFS Schedule FeedCTA publishes a GTFS (General Transit Feed Specification) schedule feed covering the physical layout, stop ...BNSF Schedules APIThe BNSF Schedules API provides intermodal transit schedules enabling customers to view planned departure a...HERE Public Transit APIMulti-modal public transit routing, station and stop lookup, departure boards, and next-departure data for ...Federal Transit Administration National Transit DatabasePublic-transportation operating, financial, and asset data submitted by transit agencies under the National...HashiCorp Vault Transit APITransit encryption-as-a-service secrets engineFlix GTFS Schedule FeedsFirst-party GTFS Schedule feeds published by FlixMobility Tech GmbH covering the FlixBus and FlixTrain netw...
Emerging 4 Early or largely undocumented
VIA Rail GTFS Schedule FeedVIA Rail's complete national timetable published as a static General Transit Feed Specification (GTFS) arch...Rome2Rio Search APIThe Rome2Rio Search API returns multi-modal door-to-door travel routes between any origin and destination w...Amtrak GTFS Schedule FeedAmtrak's complete national timetable published as a static General Transit Feed Specification archive, serv...Metra GTFS APIThe Metra GTFS API provides both raw data and JSON for Metra commuter rail schedules, trips, stops, and rea...
Score breakdown
Frequency
43.5
log-scaled weighted occurrences
Breadth
0.8
spread across providers
Quality lift
31.7
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor
Related tags
GTFS 10 co-occurrences
Public Transportation 8 co-occurrences
Stops 6 co-occurrences
Bus 5 co-occurrences
Rail 6 co-occurrences
Vehicles 6 co-occurrences
Routes 5 co-occurrences
Mobility 10 co-occurrences
Where this tag comes from
Api tag13
Provider tag24
Openapi tag1
Openapi op tag5
Cohort brief
Auto-generatedThe 31 providers in the APIs.io catalog tagged Transit, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
Providers
31
all scored
Mean Kin Score
26.2
+5.5 vs catalog 20.7
Mean Agent Readiness
14.1
+4.4 vs catalog 9.7
Spread
5–60.6
median 27.9 · σ 13.2
How the 31 split by band
Exemplar 0Strong 1Developing 2Thin 14Emerging 8Minimal 6
Facet averages, against the whole catalog
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 29.5 | 17.5 | +12 | 31 |
| Discoverability | 67 | 60.4 | +6.6 | 31 |
| Developer Ergonomics | 20.5 | 17.9 | +2.6 | 31 |
| Access Clarity | 24.7 | 22.3 | +2.4 | 31 |
| Operational Transparency | 12.9 | 11.3 | +1.6 | 31 |
| Contract Governance | 5.5 | 6.4 | -0.9 | 31 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
What this cohort publishes
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 6% | 16% | -10 |
| MCP server (first-party) | 3% | 7% | -4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 0% | 9% | -9 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 23% | 13% | +10 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
Top by Kin Score
- 1 Amazon Web Services (AWS) 60.6
- 2 Optibus 48.2
- 3 SK Telecom 44.5
- 4 Walk Score 38.5
- 5 Chicago Transit Authority 37.7
- 6 OneBusAway 36.5
- 7 Transit 36.3
- 8 Sound Transit 34.2
- 9 MBTA 34
- 10 US Department of Transportation 32.7
Top by Agent Readiness
- 1 SK Telecom 43.7
- 2 BNSF 34.2
- 3 Optibus 30.8
- 4 Walk Score 28.7
- 5 Metro Transit 23
- 6 Chicago Transit Authority 22.9
- 7 MBTA 22.9
- 8 OneBusAway 22.9
- 9 Transit 22.9
- 10 Moovit 20
All 31 members of this roster resolve to a scored provider in
the catalog.Generated from the catalog build of
25 August 2026, across 26891
providers, using the same computation served by the
APIs.io cohort API. Briefs are published for rosters of
5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This tag
curl "https://apis.io/api/v1/tags/transit"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/transit"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/transit/stats" \
-H "X-API-Key: $APIS_IO_KEY"Discovery needs no key. Ratings and market analysis are Pro.