Lalafly

Use this when you need the progress or results of a searchId returned by live_search, scoped to the connected account. This is a data/progress tool; use show_flights to present the registered flight cards. The UI calls this for progress without remounting. Never initiate another search to poll. Preserve accessNotice, coverage, timestamps, partial status and exact ticket URLs. A plan restriction is terminal and not a sign-in error. After completion, refreshOffer is a separate live search and requires explicit user acceptance of its cost.

live_search_results

Use this when the user asks for passagens, voos, flights or award availability with miles from Brazil on specific travel dates or a date range, including holiday trips such as GRU to Boa Vista (BVB) for Réveillon, or when cached route fares are missing. First use search_programs to show choices and ask which programs they use, unless they have already chosen in this conversation. Do not start until they choose programs or explicitly compare all. Requires a connected Lalafly account before starting any work. Accounts use their normal allowance. Do not ask connected users to sign in again. When loadingNotice is present, explain immediately that the programs are being queried in real time and fares appear as programs respond, before polling. If accessNotice is returned, this is a terminal response (done: true): immediately answer the user with its message and informationLink in this same turn, even when isError is true. Do not poll, retry, reconnect, or wait for a follow-up message. Do not call the result empty or offer a checkout. Before asking dates, ask 'Só ida ou ida e volta?' unless the user already said; do not require a return for a one-way request. If the user answers a date question with a bare range (e.g. '28 a 2 de jan'), confirm whether it means departing any day in that range or departing on the first date and returning on the last. Date limits per leg: one exact date, except Pro, which allows up to ±5 days (11 dates); ask the user to narrow the dates instead of sending a wider range. If the user asks to include the return after a one-way search (roundTripOffer), ask for the return date and call live_search again with the same inputs plus returnDateStart. Connected searches use the account's plan, credit and date limits. Only a started search returns searchId and actual coverage; call show_flights once for that searchId only when accessNotice is absent. The registered component reads live_search_results for progress. Never replace this search with web cash fares.

live_search

Use this when the user asks about points transfer bonuses (transferência bonificada), now or in the past: which bonuses are running, how many miles their points become, the biggest bonus a pair ever had, the usual bonus, or when it last happened (e.g. Livelo, Esfera or Itaú to Smiles, LATAM Pass or Azul). bonuses lists the campaigns valid today, each with pointsPerMile and milesPer1000Points for non-club members. ratios lists the official points-per-mile ratio of every pair, with or without a campaign. history summarizes every pair Lalafly has recorded (campaignsSeen, bestBonusPct, averageBonusPct, lastSeen); pass from and/or to to also get each matching pair's campaigns one by one and the bank points purchase cost. Campaigns change weekly: never answer from memory.

transfer_bonuses

Use this when the user asks where they can fly with miles from a Brazilian city, or wants destination ideas within a miles budget. Returns the cheapest one-way award fares per destination, plus the cheapest one in the user's own programs when that differs.

cheapest_destinations

Use this when the user starts a flight search with miles and has not yet said which programs they use: it opens the registered Lalafly program picker. The component shows every program unchecked. With Premium or Pro the user can pick several or compare all; otherwise a search uses one program, and the component offers one at a time. Do not generate a second form, checkboxes or program list in the assistant response. Let the user choose in this component before starting or charging a live search. Account favorites are suggestions, not a confirmed choice. Skip this tool if the user already specified their programs in this conversation.

search_programs

Use this when the user asks which Lalafly account is connected, or which miles programs and bank points they have.

my_account

Use this when live_search has returned a searchId without accessNotice: call it once to display Lalafly's registered flight cards. It reads the owned saved search and never starts or charges another search. The component shows flight schedules, mileage prices, taxes, approximate BRL and exact ticket links, and reads progress while programs are running. Do not generate HTML/JSX, forms, duplicate cards, tables or a second result list in the assistant response. Keep the accompanying text brief. Also use this to reopen an existing saved search as cards. Plan restrictions are terminal and must be shown with their informational link, without asking for sign-in again.

show_flights

Use this when the user asks for the best award flight deals or promotions right now (ofertas, promoções de passagem com milhas). Returns round trips from Brazil priced at least 30% below the route's usual cost, or exceptional for the cabin, seen in the last 3 days.

todays_deals

Use this when the user asks how many miles a route costs in general, its cheapest program or cheapest month, without specific travel dates. For flight requests with dates, holidays (e.g. Réveillon) or insufficient cached fares, use live_search instead; it requires a connected Lalafly account. Origin must be in Brazil. Fares include the user's program and bank-points preferences.

route_miles