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.

🌐 Visit website 📡 Source on GitHub

23.7/100 emerging ▬ flat Agent 23/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0

AccessFreeOpen⚡ Free to try

4 APIs

MinneapolisMinnesota Public Transportation Real-Time Transit

Kin Score

Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0

Composite quality — 23.7/100 · emerging

Contract Quality 8.5 / 25

Developer Ergonomics 3.8 / 20

Access Clarity 2.6 / 20

Operational Transparency 1.4 / 13

Contract Governance 0.0 / 12

Discoverability 7.4 / 10

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Surface 0 / 5

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/metro-transit: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Rate Limits 1

Documented rate limits and quota policies.

Metro Transit Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Company 2

The organization behind the API

LinkedIn

Website

Website

Source (apis.yml)

aid: metro-transit
name: Metro Transit
description: 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.
type: Index
accessModel:
  pricing: free
  onboarding: open
  trial: false
  try_now: true
  public: true
  label: Free · Open access
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/metro-transit.png
tags:
- Minneapolis
- Minnesota
- Public Transportation
- Real-Time
- Transit
url: https://raw.githubusercontent.com/api-evangelist/metro-transit/refs/heads/main/apis.yml
created: '2025-05-02'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: metro-transit:metro-transit-alerts-api
  name: Metro Transit Alerts API
  description: The Alerts API from Metro Transit — 3 operation(s) for alerts.
  humanURL: https://svc.metrotransit.org/swagger/index.html
  baseURL: https://svc.metrotransit.org/nextripv2
  tags:
  - Alerts
  properties:
  - type: OpenAPI
    url: openapi/metro-transit-alerts-api-openapi.yml
  - type: Documentation
    url: https://svc.metrotransit.org/swagger/index.html
- aid: metro-transit:metro-transit-nextrip-api
  name: Metro Transit NexTrip API
  description: The NexTrip API from Metro Transit — 8 operation(s) for nextrip.
  humanURL: https://svc.metrotransit.org/swagger/index.html
  baseURL: https://svc.metrotransit.org/nextripv2
  tags:
  - NexTrip
  properties:
  - type: OpenAPI
    url: openapi/metro-transit-nextrip-api-openapi.yml
  - type: Documentation
    url: https://svc.metrotransit.org/swagger/index.html
- aid: metro-transit:metro-transit-planner-api
  name: Metro Transit Planner API
  description: The Planner API from Metro Transit — 8 operation(s) for planner.
  humanURL: https://svc.metrotransit.org/swagger/index.html
  baseURL: https://svc.metrotransit.org/nextripv2
  tags:
  - Planner
  properties:
  - type: OpenAPI
    url: openapi/metro-transit-planner-api-openapi.yml
  - type: Documentation
    url: https://svc.metrotransit.org/swagger/index.html
- aid: metro-transit:metro-transit-schedule-api
  name: Metro Transit Schedule API
  description: The Schedule API from Metro Transit — 5 operation(s) for schedule.
  humanURL: https://svc.metrotransit.org/swagger/index.html
  baseURL: https://svc.metrotransit.org/nextripv2
  tags:
  - Schedule
  properties:
  - type: OpenAPI
    url: openapi/metro-transit-schedule-api-openapi.yml
  - type: Documentation
    url: https://svc.metrotransit.org/swagger/index.html
common:
- type: AgenticAccess
  url: agentic-access/metro-transit-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/metro-transit-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/metro-transit-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/metrotransit
- type: LinkedIn
  url: https://www.linkedin.com/company/metro-transit
- type: Portal
  url: https://www.metrotransit.org/developer-resources
- type: Documentation
  url: https://svc.metrotransit.org/swagger/index.html
- type: Website
  url: https://www.metrotransit.org/
- type: Integrations
  url: https://www.metrotransit.org/integrations
integrations:
- name: metro transit on X
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/metro-transit"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/metro-transit/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/metro-transit/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.