Cleartrip

`search_flight` - Live flight search with processed response (flights cards, searchId, dataId, totalFlightsAvailable, displaying, metaData, selectionGuide, isRoundTrip). When to use: When a user requests real-time flight availability, pricing, or schedules between two cities. This is the primary search tool. When NOT to use: If you only need to check the rules or final price of a flight the user has already selected (use `fetch_fare_options` instead). Flow position: * Requires: None (entry-point tool). * Next step: Present the `flights` table to the user. **Wait for the user to explicitly select a flight.** After user selects, use `selectionGuide.options` to look up the `cardId` and `travelOptionId` for that flight. Then call `fetch_fare_options` with `travelOptionId` (as `travel_option_id`) and the `dataId` from the response (as `data_id`). Never auto-select — always wait for user input before calling `fetch_fare_options`. Returns (processed external response): * `searchId` (string): Readable correlation id (e.g. `DC_Search-<uuid>`); pass as `search_id` only where explicitly required. * `dataId` (string): **Required opaque token** — pass exactly as returned as parameter `data_id` to `fetch_fare_options` and `create_itinerary`. **Never substitute `searchId` for `dataId`** — wrong id causes HTTP 500. If `dataId` is absent, re-run `search_flight`. * `flights` (array): Result cards. Each card contains exactly: `journeyId`, `cardId` (integer), `travelOptionId` (integer), `flights` (flight number label e.g. `'AI101 → SG456'`), `departure` (`{airport, time}`), `arrival` (`{airport, time}`), `duration` (string e.g. `'2h 30m'`), `stops` (integer), `price` (total INR), `currency` (`'INR'`), `segments` (list of `{flightNumber, airlineCode}`). **Fields NOT present in this response:** `layovers`, `timeline`, `terminal`, `sortData`, `filterData`, `aircraftType`. Do not reference or invent these fields. * `totalFlightsAvailable` / `displaying`: Count of all matching flights vs how many are shown. * `viewMoreUrl`: Cleartrip URL to see all results; show this to the user so they can browse further. * `metaData`: Lookups — `airlineDetail` and `airportDetail` maps keyed by IATA codes. * `selectionGuide` (object): **Use this to look up IDs after user selects a flight.** Contains: - `dataId`: same as top-level `dataId` — pass as `data_id` to downstream tools. - `searchId`: same as top-level `searchId`. - `options` (array): one entry per displayed flight with `flight` (label), `cardId`, `travelOptionId`, `journeyId`, and `price`. **Always read `travelOptionId` from here — never invent it.** * `isRoundTrip` (boolean, if round-trip): `true` when J2 cards are present; `flights` will contain cards for both J1 (outbound) and J2 (return). Call `fetch_fare_options` once per leg. Display Rules: Present `flights` in a table sorted by increasing price. Show at minimum: flight code (`flights`), departure airport + time, arrival airport + time, duration, stops, price (INR). For round-trip, show J1 and J2 in separate tables. Always show `viewMoreUrl` so the user can see more options on Cleartrip. Constraints: ⚠️ Special Restrictions: * Cleartrip For Work fares are mutually exclusive with `special_fare_type`. * Origin and destination airports cannot be the same. * The search date must not be in the past. * `STUDENT` and `SENIOR_CITIZEN` fares cannot be combined with `children` or `infants`.

search_flight