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 API contracts indexed 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.

The Metro Transit catalog on APIs.io includes 1 Spectral governance ruleset.

Metro Transit’s developer surface includes engineering blog, developer portal, documentation, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

24.7/100 emerging ▬ flat Agent 22/100 agent aware Front door AI 1/6 silent Heartbeat 67/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreeOpen⚡ Free to try

4 published contracts

MinneapolisMinnesota Public Transportation Real-Time Transit

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 24.7/100 · emerging

Contract Quality 6.9 / 19

Developer Ergonomics 3.2 / 15

Access Clarity 0.6 / 15

Operational Transparency 2.1 / 10

Contract Governance 1.2 / 9

Discoverability 5.4 / 8

Regulatory Posture 1.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 22/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 Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/metro-transit/"><img src="https://apis.io/badge/metro-transit/card.svg" alt="Metro Transit on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 4.3 — up to +19.1 composite points Ask about this →
Contract Quality scores 36.7 — up to +15.8 composite points Ask about this →
Developer Ergonomics scores 21.4 — up to +15.7 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/metro-transit/apis.yml: open an issue on github.com/api-evangelist/metro-transit to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Transit and Mobility (public transit, rail, micromobility)	standard	17.2 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

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 8

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Service Alerts API

OPEN COLLECTION

Service Alerts API

OPEN COLLECTION

Service Alerts NexTrip API

OPEN COLLECTION

NexTrip API

OPEN COLLECTION

Service Alerts Planner API

OPEN COLLECTION

Service Alerts Schedule API

OPEN COLLECTION

Schedule API

OPEN COLLECTION

Trip Planner API

OPEN COLLECTION

Scroll for all 8

Metro Transit API pricing

Not yet checked against Metro Transit's own pricing page. Compiled by API Evangelist on 2026-05-05 from svc.metrotransit.org/; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Open Data freemium	Free

Plan details, limits and sources →

Rate limits

GTFS-realtime poll cadence: recommended cadence 1 poll per 5 seconds (feed refresh interval) requests per second
GTFS static refresh: recommended once per Saturday refresh (use Last-Modified) requests per week
REST API: no documented hard limit; observe fair-use requests per second

Compiled by API Evangelist, not yet checked against Metro Transit's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Metro Transit Plans Pricing

1 plans

PLANS

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.

Metro Transit Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Metro Transit API Rules

38 rules · 33 error-severity 4 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Metro Transit Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Metro Transit Vulnerability Disclosure

no policy recorded

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Metro Transit Agentic Access

24 operations · 6 acting

AGENTIC

Resources

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

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Blog

Blog

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
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: open
  trial: false
  try_now: true
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Free · Open access
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  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-10-06'
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: Plans
  url: plans/metro-transit-plans-pricing.yml
- type: RateLimits
  url: rate-limits/metro-transit-rate-limits.yml
- type: FinOps
  url: finops/metro-transit-finops.yml
- url: https://www.metrotransit.org/news/
  type: Blog
- 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

Metro Transit API — frequently asked questions

Does Metro Transit have an API?

Yes. APIs.io lists 4 APIs from Metro Transit, including Metro Transit Alerts API, Metro Transit NexTrip API and Metro Transit Planner API, and 1 more.

Is there an OpenAPI specification for the Metro Transit API?

Yes. APIs.io indexes 4 OpenAPI specifications for Metro Transit, each linked for download from this page.

How much does the Metro Transit API cost?

APIs.io lists 1 pricing plan for Metro Transit, with each plan's price, limits and inclusions under Pricing on this page.

Is the Metro Transit API ready for AI agents?

Metro Transit has a Kin Score of 24.7 out of 100 (emerging) and an Agent Readiness score of 22.0 (agent-aware), scored by API Evangelist on 2026-11-13.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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