Reagent Travel

Returns the next-best flight itinerary option(s) from an existing search based on the specified feature improvement dimension(s), if next-best option(s) exist. Use only to get improved itinerary results, not to inspect or verify already-returned itineraries. The initial call (when no prior results exist) returns 1–5 top results. Each subsequent call returns the next-best itinerary option(s) based on the requested feature improvement(s), refining results across calls and surfacing strong alternatives when tradeoffs are required. Use the relevant current itinerary's position (as shown in the UI list) when requesting improvements. Call no more than once per turn after obtaining the first result set.

Starts a live flight search for available itineraries. Call this when the user wants to find flights, book a flight, search flights, compare flights, or look for plane tickets. Call when origin, destination, and departure date are known or can be safely inferred. If an arrival preference is given, infer the departure date required to arrive then, which may be before the stated arrival date; never use the arrival date as the departure date unless they are necessarily the same. Ask a clarifying question only when a required value is missing or ambiguous, such as unclear origin/destination, an outbound or return date range instead of a single date, unclear one-way vs round-trip, or a departure day that cannot be safely inferred. Do not ask for optional preferences or confirmation before searching. Use only for one-way and round-trip flights, not multi-city flights, lodging or ground/sea transportation. After this succeeds, call get_next_best_itinerary to retrieve options. Call no more than once per turn.