choose between MDS provider api and MDS agency api integration patterns for a scooter operator

Steps

1. Use the Provider API when the agency pulls historical/near-real-time data from the operator: authenticate with a bearer JWT carrying a provider_id claim, and expose /vehicles, /vehicles/status, /trips, /events/historical, /events/recent, and /telemetry.
2. Use the Agency API when the operator instead pushes updates to the regulator as events happen — same JWT/provider_id auth model, but with the data flow direction reversed.
3. Register a given provider_id for exactly one mobility mode (e.g. micromobility vs. car share vs. delivery robot); use a separate provider_id per mode if you operate more than one.
4. For /trips and /events/historical, query by an hour-bucketed end_time / event_time parameter (YYYY-MM-DDTHH) — these endpoints return 404 for hours not yet elapsed, 202 if that hour's data isn't processed yet, and 200 with an empty array if there's nothing to report.
5. Keep publishing a public GBFS feed for consumer-facing apps alongside the authenticated MDS endpoints — GBFS is not replaced by MDS Provider/Agency, and MDS is treated as the source of truth for compliance when both are used.