Search Transportation
search_transportationFull Description
Search and compare bus, train, shuttle, and ferry schedules worldwide with comprehensive filters and transparent pricing. Results render in a rich, list view showing origin and destination stop as well as departure time, trip duration and price in the currency of the user's choice for side-by-side comparison.
Autoset guidance (server-side, case-insensitive intent detection):
- Origin/Destination: ALWAYS disambiguate ambiguous locations (YOU MUST provide uniquely identifiable locations or airport codes). Always specify city name with state/province/region and country:
Examples: "Paris" → clarify "Paris, TX, USA" vs "Paris, TN, USA" vs "Paris, Ile-de-France, France" "London" → clarify "London, England, United Kingdom" vs "London, ON, Canada"
CRITICAL TEMPORAL RULES:
- If current date is before requested date → prompt the user to use a date in the future
- If requested month is before current month → use NEXT year
- If today is 2025-12-15 and user asks "trips in January" → use 2026-01-01
- For relative dates: "next week" → add 7 days, "next month" → add 1 month
- When ambiguous, default to the NEAREST FUTURE occurrence that satisfies constraints
Examples (intent → autosets)
- "Paris to London on June 1st 2026" -> origin_name="Paris, France" destination_name="London, UK" departure_date="2026-06-01"- "Montreal to London on January 1st 2026" -> origin_name="Montreal, QC, Canada" destination_name="London, ON, Canada" departure_date="2026-01-01"
Parameters
departure_datestringThe departure date in ISO 8601 format (e.g. 2026-01-01)
destination_namestringThe unambiguous destination city or location name (e.g. airport code or city, region, country) from which the trip ends. Example: "YUL", "London, England, United Kingdom", "San Jose, CA, USA"
origin_namestringThe unambiguous origin city or location name (e.g. airport code or city, region, country) from which the trip begins. Example: "Paris, Ile-de-France, France", "CDG", "San Jose, CA, USA"