@gojinko/plugin 2.1.0 → 2.2.0

package/.claude-plugin/plugin.json

@@ -1,12 +1,12 @@
 {
   "name": "jinko",
   "description": "Search flights, book trips, and manage bookings with the Jinko Travel API. Connects to the Jinko MCP server for live flight pricing, trip management, and payment.",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"
   },
-  "homepage": "https://builders.gojinko.com",
+  "homepage": "https://gojinko.com",
   "repository": "https://github.com/gojinko/jinko-dev-tools",
   "license": "MIT",
   "keywords": [

package/.codex-plugin/plugin.json

@@ -1,12 +1,12 @@
 {
   "name": "jinko",
   "description": "Search flights, book trips, and manage bookings with the Jinko Travel API. Connects to the Jinko MCP server for live flight pricing, trip management, and payment.",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"
   },
-  "homepage": "https://builders.gojinko.com",
+  "homepage": "https://gojinko.com",
   "repository": "https://github.com/gojinko/jinko-dev-tools",
   "license": "MIT",
   "keywords": [

package/README.md

@@ -12,7 +12,7 @@ Plugin for **Claude Code** and **OpenAI Codex** that enables flight search, trip
 
 ### 1. Get an API key
 
-Sign up at [builders.gojinko.com](https://builders.gojinko.com) and create an API key from the dashboard.
+Sign up at [gojinko.com/dashboard](https://gojinko.com/dashboard) and create an API key from the dashboard.
 
 ### 2. Set your API key
 

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "@gojinko/plugin",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Jinko Travel plugin for Claude Code and OpenAI Codex — flight search, booking, and trip management via MCP",
   "private": false,
   "license": "MIT",
   "author": "Jinko <dev@gojinko.com>",
-  "homepage": "https://builders.gojinko.com",
+  "homepage": "https://gojinko.com",
   "repository": {
     "type": "git",
     "url": "https://github.com/gojinko/jinko-dev-tools",

package/skills/account/SKILL.md

@@ -5,13 +5,13 @@ description: Set up and manage your Jinko developer account — registration, AP
 
 # Developer Account
 
-Manage your Jinko developer account via the [Jinko Builders Dashboard](https://builders.gojinko.com).
+Manage your Jinko developer account via the [Jinko Dashboard](https://gojinko.com/dashboard).
 
 Account management is handled through the web dashboard — there are no MCP tools for account operations. Guide the user to the dashboard for any account-related tasks.
 
 ## Getting started
 
-1. **Register** — go to [builders.gojinko.com](https://builders.gojinko.com) and sign up with your email.
+1. **Register** — go to [gojinko.com/dashboard](https://gojinko.com/dashboard) and sign up with your email.
 2. **Create an API key** — in the dashboard, go to API Keys and create a new key. The full key (prefixed `jnk_`) is shown only once — save it immediately.
 3. **Set your key** — configure your environment:
    - CLI: `jinko auth login` (OAuth) or set `JINKO_API_KEY=jnk_...`

package/skills/cli/SKILL.md

@@ -135,5 +135,5 @@ jinko refund status --ref JNK-A7B3X9 --last-name Doe
 ## See also
 
 - MCP-tool equivalents: sibling skills `search-flights`, `search-hotels`, `book-trip`, `manage-booking`
-- API docs: `https://builders.gojinko.com/docs`
+- API docs: `https://docs.gojinko.com`
 - Source: `packages/cli/src/commands/` in the `jinko-dev-tools` repo

package/skills/search-flights/SKILL.md

@@ -9,13 +9,14 @@ You have access to Jinko MCP tools for flight discovery. Pick the right one base
 
 ## Tool Selection
 
-| User intent | Tool to use |
-|-----------|-------------|
-| Nothing in mind — wants inspiration | `find_destination` |
-| Route known, flexible on dates — wants the full price-per-date list | `flight_calendar` |
-| Route known, flexible on dates — wants a short curated spread of date options ("when should I fly?") | `find_dates` |
-| Route + exact dates, wants live pricing + bookable token | `flight_search` (see the `book-trip` skill) |
-| Route + exact dates, **wants to track price over time** | `price_monitoring` |
+| User intent                                                                                          | Tool to use                                 |
+| ---------------------------------------------------------------------------------------------------- | ------------------------------------------- |
+| Nothing in mind — wants inspiration                                                                  | `find_destination`                          |
+| Route known, flexible on dates — wants the full price-per-date list                                  | `flight_calendar`                           |
+| Route known, flexible on dates — wants a short curated spread of date options ("when should I fly?") | `find_dates`                                |
+| Route + **fixed** date — wants the cheapest fares for that exact day (cached)                        | `lowest_fare`                               |
+| Route + exact dates, wants live pricing + bookable token                                             | `flight_search` (see the `book-trip` skill) |
+| Route + exact dates, **wants to track price over time**                                              | `price_monitoring`                          |
 
 > `find_flight` (cached search by route + dates) still exists for backwards compatibility but is no longer recommended — `flight_search` returns live prices and a `trip_item_token` in a single step.
 
@@ -24,10 +25,12 @@ You have access to Jinko MCP tools for flight discovery. Pick the right one base
 Discover destinations from origin airports. Returns destinations sorted by cheapest flight.
 
 **Required params:**
+
 - `origins`: array of IATA codes (include all nearby airports, e.g. `["JFK", "LGA", "EWR"]` for NYC)
 - `trip_type`: `"oneway"` or `"roundtrip"`
 
 **Optional params:**
+
 - `destinations`: filter to specific destinations
 - `departure_dates` or `departure_date_ranges`: when to depart
 - `return_dates` or `return_date_ranges`: when to return (roundtrip)
@@ -44,6 +47,7 @@ Discover destinations from origin airports. Returns destinations sorted by cheap
 Show cheapest prices across a date range for a specific route. Great for "what's the cheapest day to fly?"
 
 **Required params:**
+
 - `origin`: IATA code (e.g. `"PAR"`)
 - `destination`: IATA code (e.g. `"NYC"`)
 - `trip_type`: `"oneway"` or `"roundtrip"`
@@ -51,6 +55,7 @@ Show cheapest prices across a date range for a specific route. Great for "what's
 - `departure_date_end`: end of range (YYYY-MM-DD)
 
 **Optional params:**
+
 - `return_date_start`, `return_date_end`: return range (roundtrip)
 - `stay_days`: exact stay duration
 - `direct_only`, `cabin_class`, `currency`
@@ -69,6 +74,18 @@ Answers "when should I fly?" — takes the **same params as `flight_calendar`**
 
 **flight_calendar vs find_dates:** use `flight_calendar` for the full price-per-date grid; use `find_dates` when you want a short, spread-out shortlist of the best date options to fly.
 
+## lowest_fare
+
+Cheapest fares for a **fixed** route + date — takes the **same params as `flight_calendar`** but, for one specific departure date (one-way, or `+ return_dates` for round-trip), returns up to **10 itineraries sorted cheapest-first**. **Cache-only.** It's the fixed-date counterpart of `flight_calendar`.
+
+**Required params:** `origins`, `destinations`, `trip_type`, `departure_dates` (a single fixed date).
+
+**Optional params:** `return_dates` (round-trip), `direct_only`, `cabin_class`, `currency`.
+
+**Response:** up to 10 full itineraries (same shape as `flight_calendar`), cheapest-first.
+
+**When to use which:** `flight_calendar`/`find_dates` for flexible dates; **`lowest_fare` when the date is fixed** and you just want the cheapest options that day.
+
 ## find_flight (legacy — prefer flight_search)
 
 Cached flight search by route + dates. Still callable for backwards compatibility with older ChatGPT App versions, but not recommended for new integrations. Use `flight_search` (in the `book-trip` skill) for the same inputs plus live pricing + a bookable `trip_item_token` in one step.
@@ -78,17 +95,20 @@ Cached flight search by route + dates. Still callable for backwards compatibilit
 Track the price of a specific route + exact dates over time. **Cache-only** — never triggers a live call. Designed for scheduled polling (cron / scheduled job) so you can act on a price drop.
 
 **Required params:**
+
 - `origin`: IATA code (e.g. `"PAR"`)
 - `destination`: IATA code (e.g. `"NYC"`)
 - `departure_date`: YYYY-MM-DD
 - `return_date`: YYYY-MM-DD (omit for one-way)
 
 **Optional filters** (use the SAME set between polls — switching filters mid-poll means you're monitoring a different route, not the same one cheaper):
+
 - `direct_only`, `cabin_class`, `max_price`
 - `include_carriers` / `exclude_carriers` (IATA 2-letter codes)
 - `currency`, `locale`
 
 **Response:**
+
 - `status: "ok"` with a `flight` block (cheapest cached itinerary matching the filters), OR
 - `status: "stale"` when the cache had no matching itinerary — retry later. **Do NOT silently fall back to `flight_search`** on stale; that's a different intent. Only call `flight_search` if the user is ready to book RIGHT NOW.