Aviasales Flight Prices

Find the airports closest to a place name or to a latitude and longitude. Use when the user asks which airport to fly into for a town, a resort, or a point on the map. `lookup_airports` only matches a name, and the nearest airport is rarely named after the town, so call this tool for that question. Feed the returned city code, not the airport code, to `search_flights` for fares. Pass either `near` (resolved against the city and airport datasets) or an explicit `latitude`/`longitude` pair.

Get prices for nearby airports and cities around a chosen route. Use when the traveller can fly from or into a different airport and wants those fares. To learn which airports are near a place, use `find_nearest_airports` first; for the named city pair only, use `search_flights`.

List the cheapest destinations reachable from a city, with a fare and dates. Use when the user asks where they can fly from a city, or wants somewhere cheap without naming a destination. For who flies into a city use `get_popular_directions`; to price one chosen route afterwards use `search_flights` or `get_prices_calendar`.

Compare prices for the days around a departure and an optional return. Use when the user already has dates and asks whether shifting a day either way would be cheaper. For one exact date use `search_flights`; for the cheapest day across a whole month use `get_prices_calendar`. This covers roughly a week around both the outbound and the return.

Get the most recently found flight prices from other travellers' searches. Use when the user wants the latest fares that just appeared, on one route or across the whole cache. For a specific trip on chosen dates use `search_flights` instead. Prices are per adult (cached); passenger parameters are encoded into each booking_link. These rows come from the older v2 shape: they name the selling `agency` rather than an airline, carry no flight number, and their booking_link is reconstructed from the route and dates.

List the cities people most often fly to a destination from, with a fare. Use when the user asks where travellers reach a city from and what that costs. The request is keyed on the destination. For where someone can fly from a city use `get_city_directions`; for prices on one known route use `search_flights`.

Get grouped calendar prices for a route, one fare per day or per month. Use when the user asks which day or month is cheapest to fly a known route. For fares on one specific date use `search_flights`; for a few days either side of dates already chosen use `get_flexible_date_prices`. Codes are IATA; use `lookup_cities` to resolve a name first. Prices are per adult (cached); passenger parameters are encoded into each booking_link.

Look up airlines by name or IATA code. Use when the user asks which airline a code belongs to, or wants the IATA code for an airline name. For an airport, city, or country code use `lookup_airports`, `lookup_cities`, or `lookup_countries`; for fares use `search_flights`.

Look up airports by name, IATA code, or city code. Use when the user names an airport or a code and needs its city, country, or coordinates. For the closest airport to a town that does not share the airport's name, use `find_nearest_airports` instead of this tool. The full dataset is ~10k airports, so always pass `search` — an unfiltered call just returns the first `limit` entries in dataset order. Results are ranked: exact code, then exact city code, then name matches, with airports you cannot actually fly to last.

Look up cities by name or IATA code and return the code flight tools expect. Use when the user names a city and a flight search needs its IATA code. For an airport code use `lookup_airports`; for the nearest airport to a place that is not itself a city, use `find_nearest_airports`. Every flight tool takes IATA codes, so this is usually the first call when the user names a place. The full dataset is ~9.6k cities, so always pass `search`. Names are only available in the requested locale: searching "Мюнхен" needs locale="ru".

Look up countries by name or two-letter country code. Use when the user asks which country a code belongs to, or wants that country's code or currency. For a city or airport code use `lookup_cities` or `lookup_airports`; this tool does not search flight prices.

Find flights whose cached fare falls inside a minimum and maximum price. Use when the user has a budget, including anywhere under a price with no destination named. Leave `destination` unset to let the budget pick the city; prices are per adult in economy. For a named route on a date or a month use `search_flights` or `get_prices_calendar`. There is deliberately no date argument: this endpoint ignores one (verified — passing a December date returns the same July and September fares), and each result carries its own `departure_at`.

Search flight prices between two cities on a date or across a month. Use when the user names both ends of a route and wants fares, a booking link, or only departures inside a time window. For the cheapest day in a month use `get_prices_calendar`; for the days around dates already chosen use `get_flexible_date_prices`; for a budget with no destination use `search_by_price_range`. Both codes must be IATA — call `lookup_cities` first if you only have a city name. For nearby airports use `get_alternative_directions`. A multi-city trip needs one call per leg. Note on passengers: the price data comes from a cache of recent searches and is always PER ADULT in economy. The adults/children/infants/trip_class parameters are encoded into each ticket's booking_link, so the link opens Aviasales with the full party pre-filled and shows the real total price. Durations: each ticket reports duration_total (full door-to-door travel time), duration_to/duration_back (pure flight time per direction) and layover_minutes (combined ground time between connecting flights; 0 for direct flights). All values are in minutes.