← Back to all apps

Jinko

Travelby Jinko SAS
Launched Feb 18, 2026 on ChatGPT

Jinko helps you find the best flight deals for your next trip.

With Jinko, get flight recommendations based on your dates, budget, or any type of trip you’re planning. Explore all your options seamlessly within a single conversation.

Try asking things like:

  • Show me the best deals for a flight from New York in January. Less than 300$ per person, return trip.
  • Recommend me a destination for Valentine's day for a 4-day trip. Direct flight only.
  • Find me the cheapest flight from New York to Paris in February for a 7 days trip.

Jinko analyzes 8 billion airfares every day to answer any travel question you may have. Unlike other travel apps, we always respond with options tailored to help you find the perfect trip.

2ChatGPT Tools
Jinko SASDeveloper
TravelCategory

Available Tools

find_destination

find_destination
Full Description

Discover the best travel destinations by finding the best flight deals from your origin location.

USE THIS TOOL WHEN :

  • The user does not know where to go
  • The user is looking for destination ideas based on specific criteria (for example: beach, family-friendly, kitesurfing)
  • The user previously asked for destination recommendations and is now asking about pricing for those options

PURPOSE: Help users discover where to travel when they don't know where to go. Focus on finding great destinations based on flight prices and availability rather than searching for flights to known destinations. This tool leverage ChatGPT intelligence to identify relevant destinations for the user based on various criteria and passing it to the tool via the destinations field.

IMPORTANT

  • DATES

All dates in query parameters (departure_dates, departure_date_ranges, return_dates, return_date_ranges) MUST be in the future. Never use past dates. Please fill as much as possible search parameters based on user intent to get best results. All departure dates MUST be for a future dates, never a past dates.

IMPORTANT

  • RE-CALL THIS TOOL when the user:
    • Asks for a different destination [city, region, country]
    • Asks for different dates
    • Asks for destination with specific criteria such beach, city trip, chill etc.
    • The user is already in fullscreen mode in the widget.

CORE FUNCTIONALITY:

  • REQUIRED: User's origin location (LLM identifies ALL nearby airports)
  • OPTIONAL: Destination filtering by specific airports/cities OR omit for global discovery mode
  • Destination Discovery Mode: When destinations is omitted/empty, searches ALL destinations globally
  • Flexible dates and stay durations for exploring options
  • Filter by budget, direct flights preference, currency, and locale
  • By default, please search roundtrip flights unless user specifies one-way. Use "one-way" in the tool ONLY when the user type explicitely one way in the query

AIRPORT IDENTIFICATION

  • CRITICAL:

LLM MUST identify and recommend ALL relevant airports for user's origin location:

  • "New York": ["JFK", "LGA", "EWR"] (3 major airports)
  • "London": ["LHR", "LGW", "STN", "LTN", "LCY"] (5 airports)
  • "Paris": ["CDG", "ORY"]
  • "Tokyo": ["NRT", "HND"]
  • "Chicago": ["ORD", "MDW"]
  • "Los Angeles": ["LAX"]
  • "San Francisco": ["SFO"]
  • "SFO": ["SFO"]

If user ask for SFO, SF or San Francisco, which means the city, please only use SFO airport code.

DESTINATION FILTERING

  • INTELLIGENT INTERPRETATION:

Destinations can be specified using IATA airport codes OR city codes (3 letters). You can mix both types:

  • Airport codes: ["JFK", "LAX", "LHR"] - searches specific airports
  • City codes: ["NYC", "LON", "PAR"] - searches all airports in those cities
  • Mixed: ["JFK", "LON", "TYO"]
  • JFK airport + all London airports + all Tokyo airports

DESTINATION LIST

  • CRITICAL:

When users mention criteria that imply a type of destination, the LLM MUST first interpret that intent and generate the appropriate list of destinations before making the tool call:

Examples:

  • "Sunny places in winter": LLM identifies warm-weather destinations: ["MIA","MCO","SAN","PHX","HNL","CUN","PUJ","PTY","LIM","GIG"]
  • "Somewhere in Asia": LLM compiles major Asian destinations: ["NRT","HND","ICN","PVG","PEK","HKG","SIN","BKK","KUL","MNL"]
  • "Beach destinations": LLM identifies beach cities: ["MIA","SAN","HNL","CUN","PUJ","SJU","NAS","MBJ"]
  • "European capitals": LLM lists capital airports: ["LHR","CDG","FRA","MAD","FCO","AMS","BRU","VIE","PRG","CPH"]
  • "Ski destinations": LLM identifies ski resort airports: ["DEN","SLC","ZRH","INN","GVA","TRN"]

If no destination filtering is specified or criteria is too broad ("anywhere", "surprise me"), leave destinations empty for global discovery mode.

TYPICAL USE CASES FOR THIS TOOL: 1. "Where should I travel from NYC next month?" : origins: ["JFK","LGA","EWR"], departure_date_ranges, destinations: [] (global discovery)

2. "Find me cheap flights from SF to Europe under $800" : origins: ["SFO"], destinations: [European airports/cities], max_price: 800

3. "I want to go somewhere warm from Chicago for a week in December" : origins: ["ORD","MDW"], stay_days: 7, departure_date_ranges, destinations: [warm destinations]

4. "Best weekend getaways from Boston?" : origins: ["BOS"], stay_days_range: {min: 2, max: 4}, destinations: [] (discover mode)

5. "Direct flights from LA to Asia" : origins: ["LAX","BUR","SNA","ONT"], destinations: [Asian airports/cities], direct_only: true

6. "Beach vacation from Seattle in summer under $600" : origins: ["SEA"], destinations: [beach destinations], max_price: 600

7. "Flights to London from New York" : origins: ["JFK","LGA","EWR"], destinations: ["LON"] (city code for all London airports)

WHEN TO NOT USE THIS TOOL

  • Never use this tool when the user asks the price for a single destination. A destination is defined as a city.

Examples : 1. ""What are the cheapest date to go NYC from PAR"?" : origins: ["CDG","ORY"], departure_date_ranges, destinations: ["JFK", "LGA", "EWR"]

2. ""Give me the chepaest flight from Los Anegles to Miami in June"?" : origins: ["LAX"], departure_date_ranges, destinations: ["MIA"]

IMPORTANT: Always provide ALL airports for both origins and (when applicable) destinations to maximize search results and find the best deals.

Parameters (2 required, 14 optional)
Required
originsarray

REQUIRED. Array of origin IATA codes (3-letter uppercase), representing either airports or cities where the trip starts. The LLM MUST detect and include all relevant nearby airports or city codes based on the user’s location. Examples: ["JFK", "LGA", "EWR"] for New York City; ["SFO", "OAK", "SJC"] for the San Francisco Bay Area; ["ORD", "MDW"] for Chicago; or a single city code like ["NYC"].

trip_typestring

REQUIRED. Type of trip: "oneway" for single-leg flights, or "roundtrip" for return flights.

Options:onewayroundtrip
Optional
cabin_classstring

Preferred cabin class. Options: "economy", "premium_economy", "business", or "first". Filters results accordingly.

Options:economypremium_economybusinessfirst
currencystring

ISO 4217 currency code (e.g., USD, EUR, GBP, JPY, CAD, AUD). Defaults to USD. Should align with the user’s location or preference.

departure_date_rangesarray

List of departure date ranges for flexible travel discovery. Use when the user mentions periods like “next month” or “spring.” Supports multiple non-contiguous ranges (OR logic). Example: [{start: "2025-12-10", end: "2025-12-15"}, {start: "2025-12-20", end: "2025-12-25"}].

departure_datesarray

List of specific departure dates in ISO 8601 format (YYYY-MM-DD). Use for searching multiple specific dates with OR logic. Example: ["2025-12-15", "2025-12-16", "2025-12-17"] for flexible date searches. Useful when user wants to check specific dates like weekends.

destinationsarray

OPTIONAL. Array of destination IATA codes (3-letter uppercase), representing either airports or cities. When a city code is provided, the LLM MUST expand it to include all associated airports. Examples: ["LHR", "LGW", "STN", "LTN", "LCY"] for London airports; ["CDG", "ORY"] for Paris; ["TYO"] for all Tokyo airports. You may mix airport and city codes: ["JFK", "LAX", "LON", "PAR"]. When omitted or empty, the system searches globally to discover the best flight deals (destination discovery mode).

direct_onlyboolean

When true, only returns nonstop (direct) flights. Useful for avoiding layovers or minimizing total travel time.

localestring

Locale code for formatting and language (e.g., "en-US", "es-ES", "fr-FR", "de-DE", "ja-JP"). Defaults to "en-US". Affects date, number, and language presentation.

max_pricenumber

Maximum total price per passenger in the selected currency. Filters out results exceeding the limit. Example: 500 = limit of $500/€500/£500 per person.

return_date_rangesarray

List of return date ranges for flexible round-trip searches. Supports multiple return windows. Example: [{start: "2025-12-22", end: "2025-12-25"}, {start: "2025-12-29", end: "2026-01-02"}].

return_datesarray

List of specific return dates for round-trip searches (YYYY-MM-DD). Must be after the corresponding departure dates. Supports multiple options (OR logic). Example: ["2025-12-22", "2025-12-23", "2025-12-24"].

sort_bystring

Sorting preference for search results. Options: "lowest" (cheapest first, default) or "recommendation" (best overall balance of price, duration, and stops).

Options:lowestrecommendation
stay_daysinteger

Exact number of days to stay at the destination. Used with a departure date to automatically compute the return date. Example: 7 = one-week trip; 3 = weekend getaway.

stay_days_rangeobject

Range of acceptable trip durations for flexible planning (e.g., “5 to 10 days”). Cannot be combined with stay_days or explicit return_date. Example: {min: 5, max: 10}.

user_querystring

The original natural-language user query that triggered this tool call. Used for context.

find_flight

find_flight
Full Description

Find and compare flights between two specific cities or airports with an interactive carousel widget displayed inline.

IMPORTANT: All dates in query parameters (departure_dates, departure_date_ranges, return_dates, return_date_ranges) MUST be in the future. Never use past dates. Please fill as much as possible search parameters based on user intent to get best results.

SPECIFIC ROUTE SEARCH: This tool searches for flights between a single origin and destination city:

  • Use exact 3-letter IATA aiprort codes or IATA city code for both origin and destination
  • Date ranges OR stay duration for flexible trip planning
  • Natural trip duration (stay_days) instead of exact return dates
  • Simplified, essential parameters focused on finding options
  • By default, please search roundtrip flights unless user specifies one-way. Use "one-way" in the tool ONLY when the user type explicitely one way in the query

USE CASES: ✓ "Find flights from JFK to CDG next month"

  • Specific route with date range

✓ "I want to fly from Los Angeles to Tokyo for a week in December"

  • Uses departure_date + stay_days

✓ "Direct flight in business class from New York to London, staying 5-10 days"

  • Uses stay_days_range

✓ "Cheapest flight from ORD to LHR under $600"

  • Specific route with budget

The widget displays flights in a scrollable carousel with options to view detailed itineraries.

Parameters (3 required, 13 optional)
Required
destinationstring

REQUIRED: Single origin airport IATA code or IATA City Code. Example for IATA airport code : "LGW" for Gatwick in London, "SFO" for San Francisco. Example for IATA city code : "LHR" for London, "BJS" for Beijing.

originstring

REQUIRED: Single origin airport IATA code or IATA City Code. Example for IATA airport code : "JFK" for John F.Kennedy in New York, "LAX" for Los Angeles. Example for IATA city code : "NYC" for New York, "PAR" for Paris.

trip_typestring

REQUIRED: Trip type: "oneway" for one-way flights or "roundtrip" for round-trip flights.

Options:onewayroundtrip
Optional
cabin_classstring

Cabin class preference. Options: "economy" (standard economy), "premium_economy" (enhanced economy with more space/amenities), "business" (business class), "first" (first class). When specified, only shows flights in the requested cabin class.

Options:economypremium_economybusinessfirst
currencystring

ISO 4217 currency code for prices (USD, EUR, GBP, JPY, CAD, AUD, etc.). Default: USD. Use currency matching the user's location or preference.

departure_date_rangesarray

List of departure date ranges for flexible travel exploration. Use when user says "next month", "spring", or wants to discover deals across multiple date periods with OR logic. Example: [{start: "2025-12-10", end: "2025-12-15"}, {start: "2025-12-20", end: "2025-12-25"}] for non-contiguous periods.

departure_datesarray

List of specific departure dates in ISO 8601 format (YYYY-MM-DD). Use for searching multiple specific dates with OR logic. Example: ["2025-12-15", "2025-12-16", "2025-12-17"] for flexible date searches. Useful when user wants to check specific dates like weekends.

direct_onlyboolean

Only show direct/nonstop flights. When true, only flights with no stops are returned. Use for fastest travel or when layovers are not desired.

localestring

Locale code for results formatting (e.g., "en-US", "es-ES", "fr-FR", "de-DE", "ja-JP"). Default: en-US. Affects date/time formatting and localized content.

max_pricenumber

Maximum total price per person in specified currency. Helps find flights within budget. Example: 500 means flights up to $500/€500/£500 per person depending on currency.

return_date_rangesarray

List of return date ranges for flexible round-trip exploration. Use when user wants flexibility on return timing across multiple periods with OR logic. Example: [{start: "2025-12-22", end: "2025-12-25"}, {start: "2025-12-29", end: "2026-01-02"}]

return_datesarray

List of specific return dates for round-trip flights (YYYY-MM-DD). Use for searching multiple return date options with OR logic. Must be after departure dates. Example: ["2025-12-22", "2025-12-23", "2025-12-24"]

sort_bystring

Sort results by this criteria. Default: lowest (best deals first). Options: lowest (cheapest flights), recommendation (best overall value considering price, duration, and stops).

Options:lowestrecommendation
stay_daysinteger

Exact number of days to stay at destination. Used with departure_date to calculate return date automatically. Example: 7 for a week-long trip, 3 for a weekend getaway.

stay_days_rangeobject

Flexible stay duration range. Use when user wants flexibility in trip length (e.g., "5 to 10 days"). Cannot be combined with exact stay_days or return_date. Example: {min: 5, max: 10}

user_querystring

The original natural-language user query that triggered this tool call. Used for context.