Model fare products and rider pricing using GTFS-Fares v2
domain: gtfs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the agency publishes Fares v2 files (fare_products.txt, fare_leg_rules.txt, fare_transfer_rules.txt, rider_categories.txt, fare_media.txt, timeframes.txt) rather than only the older Fares v1 fare_attributes.txt/fare_rules.txt
Read the current extension reference at gtfs.org/community/extensions/fares-v2/
Use timeframes.txt with fare_leg_rules.txt to resolve time-of-day fare variation such as rush-hour pricing
Use rider_categories.txt to compute discounted fares for seniors, students, or other categories
Use fare_media.txt/fare_products.txt to distinguish container types (paper ticket, contactless card, mobile app) that affect which price applies
Known gotchas
Fares v1 and v2 files can coexist in an agency's feed during migration — check which files are actually populated before assuming full v2 coverage
Fare computation is leg-based, not trip-based; a single rider trip may require combining fare_leg_rules and fare_transfer_rules across multiple legs
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?