Metro Transit
Metro Transit provides real-time departure information, service alerts, trip planning, and schedule data APIs for the Minneapolis-Saint Paul metropolitan transit system. The APIs support creating transit departure displays and accessing real-time bus and train arrival data for the Twin Cities.
Metro Transit publishes 4 APIs on the APIs.io network, including Alerts API, NexTrip API, Planner API, and 1 more. Tagged areas include Minneapolis, Minnesota, Public Transportation, Real-Time, and Transit.
Metro Transit’s developer surface includes developer portal, documentation, and 6 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Metro Transit Alerts API
The Alerts API from Metro Transit — 3 operation(s) for alerts.
Metro Transit NexTrip API
The NexTrip API from Metro Transit — 8 operation(s) for nextrip.
Metro Transit Planner API
The Planner API from Metro Transit — 8 operation(s) for planner.
Metro Transit Schedule API
The Schedule API from Metro Transit — 5 operation(s) for schedule.
Open Collections 9
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONService Alerts API
OPEN COLLECTIONService Alerts API
OPEN COLLECTIONService Alerts NexTrip API
OPEN COLLECTIONNexTrip API
OPEN COLLECTIONService Alerts Planner API
OPEN COLLECTIONService Alerts Schedule API
OPEN COLLECTIONSchedule API
OPEN COLLECTIONTrip Planner API
OPEN COLLECTIONScroll for all 9
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Metro Transit Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Metro Transit Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.