Get live flight pricing, search by route, or re-price a known offer
Fetch live, bookable pricing for a specific route and date pair. Use it once the user has settled on exact travel dates, for example “Paris to New York departing June 1 returning June 8 in economy”. It also reprices an offer surfaced earlier by the calendar or destination tools so you can confirm availability before adding it to a trip.
Tool description (what the LLM sees)
Get live flight pricing and fare options. Provide exactly one of the "search" or "price_check" nested objects:1. search: Live flight search by route and dates. Example: { "search": { "origin": "PAR", "destination": "NYC", "departure_date": "2025-06-01" } } Required fields: origin, destination, departure_date. Optional: return_date, cabin_class, direct_only, origin_type, destination_type.2. price_check: Get live pricing for a specific flight deal from discovery tools (flight_calendar, find_destination, flight_calendar). Example: { "price_check": { "offer_token": "token_from_discovery" } }IMPORTANT: "search" and "price_check" are nested objects, not string values. Do NOT pass them as strings.RESPONSE:- Each flight includes detailed segments, fare options with baggage/refund/change rules, and a trip_item_token per fare.- price_check may return status "flight_unavailable" with alternatives if the flight is no longer available, ask the user to choose.NEXT STEP: Use the trip tool with add_item and the trip_item_token from the fare the user selects.Flow: discovery (flight_calendar / find_destination / flight_calendar) or direct search → flight_search → trip → checkoutPRICES: prices in the response are preformatted strings like USD 180.90, display them as-is; there are no minor-unit integers to convert.
Live flight search by route and dates. Use city codes by default (PAR, NYC); use airport codes (CDG, JFK) only when the user specifies a particular airport.
search.origin
string
Yes
Origin IATA city code (e.g. PAR, NYC, LON) or airport code (e.g. CDG, JFK, LHR). City codes preferred, they search all airports in the city.
search.origin_type
enum ("city" | "airport")
No
Whether origin is a city code or airport code. Defaults to “city”.
search.destination
unknown
Yes
Destination IATA city code (e.g. MIL, BCN, TYO) or airport code (e.g. MXP, BCN, NRT). City codes preferred.
search.destination_type
enum ("city" | "airport")
No
Whether destination is a city code or airport code. Defaults to “city”.
Max results to return (1-100). Default 20. Caps how many flights come back; only trims the set, since providers bound the real count.
price_check
object
No
Get live pricing for a specific flight deal. Returns confirmed fares with trip_item_token for booking.
price_check.offer_token
string
Yes
offer_token from flight_calendar, find_destination, or flight_calendar results.
passengers
object
No
Passenger counts. Defaults to 1 adult.
passengers.adults
integer
No
Adult travelers (12+)
passengers.children
integer
No
Child travelers (2-11)
passengers.infants
integer
No
Infant travelers (under 2)
currency
string
No
ISO 4217 currency code. Defaults to “USD”.
locale
string
No
BCP 47 locale. Defaults to “en-US”.
user_intent
string
No
The end user’s current request in their own words, e.g. “find a cheap flight to Tokyo in mid-June”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional and never changes the result of the call; Jinko uses it to understand demand and improve results.
The response has detailed segment info per itinerary and multiple fare options per itinerary (economy / premium / business), each with a trip_item_token you pass to trip(add_item).
If price_check returns status: "flight_unavailable", the offer sold out, use the alternatives[] in the response or loop back to discovery.
