Doorfarer

Finds trips for a group whose people leave from different towns to meet in one place on the same dates: each person's own door-to-door trip (the train, bus or car to their best airport, and the flight), one line per town, with the group's total, the longest journey and the dates that work for everyone. E.g. "Four of us want a week in Lisbon in May: two from New Haven, one each from Ithaca and Burlington." Put each town once in homes with how many people leave from it. For "where should we meet?" pass a region, countries or "anywhere" as destinations with anywhere true. For one home town, use find_trips. A month without a year means the next one coming. With no dates from the group this tool runs no search and returns the question to ask; once they name a time, or say any time suits them (flexible true), it searches. A month is enough to search: don't ask for exact dates. If a search finds nothing, say so and offer a wider window or single-town searches; never quote prices from other sources.

Finds the best round trips from where someone lives, not just from one airport: it adds the train or bus to every airport they can reach and ranks all options door to door, by price, by total travel time, or balanced. Use it when someone wants flights from their home town, could fly from several airports, or asks for the cheapest or fastest way to get somewhere, e.g. "I live in New Haven: should I fly to Lisbon from JFK, Newark, Boston or Hartford?" Not for a search from one airport already chosen. For a one-way trip set one_way (the trip length is then ignored). Multi-city: search each leg as one_way only when the user gave dates for it; otherwise ask for the dates. Set mode only when the user says how they get to the airport (car, train, bus, any): by default a home in the US compares driving, a taxi to a near airport and public transport, and a home elsewhere uses the train or bus. A named departure airport is an ordinary search: pass it as from_airports, with the home town the user gave. Ask when and for how long first: with no dates from the user this tool runs no search and returns the question to ask (and a form); it searches once the user names a time, or says any time suits them (dates "flexible"). A month or holiday without a year means the next one coming; don't ask which year or to confirm a town. Travellers default to 1 and the trip length to 2-14 nights; the answer's summary names both. Any town or village works. The first search from a town we haven't seen takes about 20 seconds while we look up its train and bus connections; tell the user you're checking the connections from their town to each airport. Later searches from that town take a second or two. Give the home town and where to: airport, city or country codes, a list of them, or a region such as "Iberia" or "Southeast Asia". For "anywhere", a continent ("Asia") or "somewhere warm" it finds the cheapest places itself: pass "anywhere", "abroad" (another country) or the continent, or for warm, s…

Shows the cheapest month to travel from someone's home town to a place, for each airport within reach: the cheapest fare found for each month (or, where none is found, what that route usually costs) plus the train or bus to the airport and the transfer into the city. Takes a few seconds. Airports further than 8.5 hours from home are left out and named. Use it when the user's dates are flexible or they ask when it's cheapest to go; then call find_trips for the month they choose to get bookable trips. Needs the home town; months as "2027-03", at most 12; for a season or a year pass its months ("next spring" = March to May), and the answer says which months have fares (state only those). Prices per person, in the home currency unless `currency` is given. The widget shows the months: reply in 3-4 sentences, with the best month and what it costs ("cheapest found" or "usual price", as the answer says), and don't quote prices from other sources.

Tell Doorfarer's maker where Doorfarer fell short, so it can be fixed. Use it when a find_trips answer was wrong, confusing, or missing something you needed to help, or when the user asks you to pass something on. Write as the assistant that used the tool: what you asked for, what came back, what you expected instead. The report is about Doorfarer only, never about the user: leave out names, contact details, travel plans, reasons for travelling and anything the user said about themselves. Be specific and honest, including when the problem may have been your own call. Pass the search_id from the answer's last line. One report per search. If the user asked you to report something, tell them it's sent.

Shows one trip from a find_trips answer step by step, door to door: leaving home, the train or bus to the airport, the airport wait, the flight, the transfer into the city and arrival, then the way back, with local times. Also gives the booking link and a calendar file (.ics) the user can add. Pass a trip id from the find_trips answer ("Trip ids, row by row", or a row's `id`); "the best one" is the find_trips answer's top pick. Use it when the user picks a trip or asks how the journey works. Ids are kept for 72 hours. The widget shows every leg, so reply in at most 4 sentences with no table: the summary line, the times that matter (leaving home, the flight, arriving) and the booking link. Don't look up flights, airports or transit elsewhere: our times come from the fare, and a layover is a connection that is part of the trip.