Flaut.Travel
Flight search, airfare analytics, flexible destination discovery and airport insights
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Resolve City Iata Code: Use this tool to resolve a city name into its corresponding city IATA code before calling any route price, monthly price, or airport analytics tool that requires a city code. I
- Discover Destinations: Data-only first step in the travel funnel. Use this tool to discover destination city ideas from traveler preferences before searching route prices. It returns city-level recomm
- Render Destinations: Render one final Flaut.Travel destination widget after all discover_destinations calls are complete. Call this tool exactly once and pass the complete structuredContent results un
What data it sees
Do you need an account
No: the server works without sign-in
Flight search, airfare analytics, flexible destination discovery and airport insights
Server tool list (8)
Raw names from tools/list. Only developers need these.
| resolve_city_iata_code | Use this tool to resolve a city name into its corresponding city IATA code before calling any route price, monthly price, or airport analytics tool that requires a city code. It returns cities only, not individual airports. |
| discover_destinations | Data-only first step in the travel funnel. Use this tool to discover destination city ideas from traveler preferences before searching route prices. It returns city-level recommendations and their city IATA codes. You may call it multiple times with different filters or pages when comparing preferences. After every relevant discovery is complete, call render_destinations exactly once with all complete structuredContent results you want displayed; do not render after each search. Budget level describes destination affordability, not flight ticket prices. After choosing a destination, call get_route_monthly_prices or search_route_prices for route pricing. |
| render_destinations | Render one final Flaut.Travel destination widget after all discover_destinations calls are complete. Call this tool exactly once and pass the complete structuredContent results unchanged, in the order they should be combined. Results must use the same locale; filters, pages, and limits may differ. The tool preserves first-seen search order, deduplicates cities, limits the final presentation to 20 destinations, and renders a clear empty state when every result is empty. The attached Flaut.Travel component is the complete authoritative presentation; do not recreate it as a separate carousel, card grid, list, or table. |
| get_route_origin_airports_analytics | Returns analytics for airports that can be used on the origin side of a route, including prices, route availability, direct flights, and airlines. |
| get_route_destination_airports_analytics | Returns analytics for airports that can be used on the destination side of a route, including prices, route availability, direct flights, and airlines. |
| get_route_monthly_prices | Returns monthly prices and an interactive Flaut.Travel price chart for a city-to-city route. The attached component is the complete and authoritative visualization: do not create another chart or table from the returned data. After the component, provide only a brief textual takeaway. Each month contains the cheapest one-way ticket found in recent user searches; null means no data for that month. |
| search_route_prices | Data-only search for cached route prices from the monolith backend. Prices are not an offer and are based on data found by users during the last 48 hours. Always set locale to the language of the user's current request, independently of market and route. Provide at least origin or destination. Use YYYY-MM for a month, season, flexible dates, or when the user did not name an exact day; use YYYY-MM-DD only when the user explicitly named that date, and never invent or sample a day. For multiple periods, call this tool once per period with the same market and trip settings. After every relevant search is complete, call render_route_prices exactly once with the complete structured results you want displayed. Empty tickets means no matching cached prices were found, not that no flights operate. Use unique=true with only origin to find the cheapest destinations from a city. Use resolve_city_iata_code first when you know a city name but not its IATA code. |
| render_route_prices | Render one final Flaut.Travel route-price widget after all search_route_prices calls are complete. Call this tool exactly once and pass the complete structuredContent results unchanged. Results must use the same route, currency, market, locale, one-way setting, sorting, and unique setting; departure dates, pages, limits, and direct-only filters may differ. The tool combines and deduplicates tickets, preserves route semantics, sorts globally by price when the searches used price sorting, and renders a clear empty state when every result is empty. The attached Flaut.Travel component is the complete authoritative presentation; do not recreate it as a separate card grid, list, or table. |