export monthly aggregated reports and CSV-based data from an MDS provider deployment
domain: github.com/openmobilityfoundation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Serve the /reports endpoint as monthly, pre-generated historic flat files named by year and month, e.g. /reports/2026-07.csv.
Set the response media type to text/vnd.mds+csv rather than the standard application/vnd.mds+json used elsewhere in MDS Provider.
Use Reports to supply aggregated data not otherwise captured by other MDS endpoints (e.g. counts of special rider groups) — Reports supplement rather than replace /trips, /events, or /vehicles.
Still return a valid MDS version and standard HTTP status codes (200/401/404/500) consistent with the rest of the Provider API.
Reference the Provider examples in the MDS repo for a concrete Reports payload shape before building your exporter.
Known gotchas
Reports use a CSV media type, not JSON like the rest of MDS Provider — a generic MDS JSON client will choke on this endpoint unless handled as a special case.
Reports are explicitly a supplement, not a substitute, for /trips or /events — don't try to derive compliance metrics solely from Reports.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?