Metro Transit · FinOps Profile

Metro Transit Finops

FOCUS-aligned FinOps shape for Metro Transit: a free, open-data API surface (GTFS, GTFS-realtime, NexTrip / REST). There is no provider-side cost to the API consumer; FinOps focus shifts to the consumer-side compute / egress / storage cost of polling and serving the public data, plus the Metropolitan Council's own publishing cost (which is not invoiced to consumers).

Metro Transit Finops is the FinOps profile for Metro Transit on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in N/A, on a n/a cycle, and pricing category free / open data.

The profile maps 7 FOCUS columns for cost-allocation reporting.

Tagged areas include Minneapolis, Minnesota, Public Transportation, Real-Time, and Transit.

Category: Public Transit Open Data Pricing: Free / Open Data Billing: N/A FOCUS v1.3
MinneapolisMinnesotaPublic TransportationReal-TimeTransitFinOpsFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

FOCUS Columns

BillingCurrency
N/A
ChargeCategory
N/A
InvoiceIssuerName
N/A (free / open data)
ProviderName
Metro Transit
PublisherName
Metropolitan Council
ServiceCategory
Public Transit Open Data
ServiceName
Metro Transit Open Data API

Meters

realtime_polls
Unit: request
Number of polls against GTFS-realtime feeds (consumer-side).
gtfs_downloads
Unit: download
GTFS static zip downloads (current + next-week + flex).
rest_requests
Unit: request
REST API requests (NexTrip, alerts, trip planner, schedule).
data_egress
Unit: GB
Bytes downloaded from svc.metrotransit.org (consumer-side accounting).

Sources