@gojinko/plugin 1.1.1 → 1.2.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "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": "1.1.1",
+  "version": "1.2.1",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "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": "1.1.1",
+  "version": "1.2.1",
   "author": {
     "name": "Jinko",
     "url": "https://gojinko.com"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gojinko/plugin",
-  "version": "1.1.1",
+  "version": "1.2.1",
   "description": "Jinko Travel plugin for Claude Code and OpenAI Codex — flight search, booking, and trip management via MCP",
   "private": false,
   "license": "MIT",

package/skills/book-trip/SKILL.md

@@ -136,7 +136,7 @@ Categories: `BAGGAGE`, `SEAT`, `MEAL`, etc.
 }
 ```
 
-Single synchronous call. The BFF schedules the quote, polls until it completes, schedules fulfillment, and returns a Stripe checkout URL. The user opens this URL in a browser to complete payment. Stripe webhooks finalize the booking automatically — no client-side confirm step is required.
+Single synchronous call. The BFF schedules the quote, polls until it completes, schedules fulfillment, and returns a canonical Jinko-hosted checkout URL of the form `https://app.gojinko.com/checkout?sid=<cart_id>`. The user opens this URL in a browser; the Jinko `/checkout` page collects any remaining info and triggers the right Stripe flow (embedded Elements or Hosted Checkout) at Pay-button click. Stripe webhooks finalize the booking automatically — no client-side confirm step is required.
 
 **Response includes:** `checkout_url`, `session_id`, `total_amount`, `items`.
 

package/skills/cli/SKILL.md

@@ -35,11 +35,12 @@ Auth alternatives:
 | `flight-search` | Live pricing — direct search by route + dates, or `--offer-token` price-check (returns bookable `trip_item_token`) |
 | `find-flight` | **Legacy.** Cached route + dates search. Kept for backwards compat; prefer `flight-search` for new work. |
 | `hotel-search` | Live hotel search by city/query/geo/hotel-ids |
+| `hotel-details` | Rich metadata (gallery, facilities, policies, per-room details) for a single hotel |
 | `trip` | Create / update a trip: add items, remove items, set travelers + contact |
 | `select-ancillaries` | Add baggage / seats / meals to a trip item |
 | `book` | Schedule checkout → returns Stripe payment URL |
 | `trip-status` | Full status: cart, quote, fulfillment, bookings |
-| `lookup-booking` | Look up a booking by `JNK-*` ref + last name (guest access) |
+| `get-booking` | Retrieve a booking by `JNK-*` ref + last name (guest access). Old name `lookup-booking` is kept as a hidden deprecated alias. |
 | `refund check / commit / status` | Voluntary refund flow |
 | `schema <command>` | Print request/response schema for a command |
 | `config` | Read/write CLI config |
@@ -61,9 +62,12 @@ jinko trip --trip-id tr_ABC \
   --travelers '[{"type":"ADT","first_name":"John","last_name":"Doe","date_of_birth":"1990-01-15"}]' \
   --contact '{"email":"john@example.com","phone":"+33612345678"}'
 
-# 4. Schedule checkout — returns Stripe URL
+# 4. Schedule checkout — returns canonical Jinko-hosted URL
 jinko book --trip-id tr_ABC
-# → { checkout_url: "https://checkout.stripe.com/..." }
+# → { checkout_url: "https://app.gojinko.com/checkout?sid=12345" }
+# The /checkout page renders the cart, collects any remaining info,
+# and triggers the right Stripe flow (embedded Elements or Hosted
+# Checkout) on Pay-button click.
 
 # 5. User pays in browser (or open the URL programmatically)
 # 6. Poll status
@@ -105,8 +109,8 @@ jinko trip --trip-id tr_ABC --remove-item-id it_123 --trip-item-token "offer_new
 ## Post-booking
 
 ```bash
-# Lookup (guest access — no auth needed beyond ref + last name)
-jinko lookup-booking --ref JNK-A7B3X9 --last-name Doe
+# Retrieve a booking (guest access — no auth needed beyond ref + last name)
+jinko get-booking --ref JNK-A7B3X9 --last-name Doe
 
 # Refund
 jinko refund check  --ref JNK-A7B3X9 --last-name Doe

package/skills/manage-booking/SKILL.md

@@ -7,9 +7,9 @@ description: Look up bookings and manage post-booking operations (refunds, cance
 
 Post-booking operations using Jinko MCP tools.
 
-## Booking Lookup
+## Get a booking
 
-Use `lookup_booking` to find a booking by its Jinko reference and the traveler's last name. No login required.
+Use `get_booking` to retrieve a booking by its Jinko reference and the traveler's last name. No login required. (Previously named `lookup_booking`; the old name is kept as a deprecated alias on the SDK and CLI.)
 
 ```json
 {
@@ -29,7 +29,7 @@ Use `lookup_booking` to find a booking by its Jinko reference and the traveler's
 
 `flight_refund` supports two auth modes — pick exactly one per call:
 
-- **Guest auth** (default for end-users): `booking_ref` + `last_name`. Works without any DevPlatform credential — the server resolves the booking via `/bookings/lookup`.
+- **Guest auth** (default for end-users): `booking_ref` + `last_name`. Works without any DevPlatform credential — the server resolves the booking via `/bookings/get`.
 - **Authenticated** (DevPlatform OAuth / `jnk_*` API keys): `order_id`. Skips the guest resolver.
 
 Do NOT mix the two modes in one call. The BFF rejects mixed combinations up front.

package/skills/search-flights/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: search-flights
-description: Search for flights, explore destinations, and compare prices across dates using the Jinko Travel API. Use when the user wants to find flights, discover where they can fly, or compare prices.
+description: Search for flights, explore destinations, compare prices across dates, and monitor a fixed route over time using the Jinko Travel API. Use when the user wants to find flights, discover where they can fly, compare prices, or track price changes on a specific route.
 ---
 
 # Flight Search
 
-You have access to three Jinko MCP tools for flight discovery. Pick the right one based on what the user knows:
+You have access to Jinko MCP tools for flight discovery. Pick the right one based on what the user knows AND what they want to do:
 
 ## Tool Selection
 
@@ -13,7 +13,8 @@ You have access to three Jinko MCP tools for flight discovery. Pick the right on
 |-----------|-------------|
 | Nothing in mind — wants inspiration | `find_destination` |
 | Route known, flexible on dates | `flight_calendar` |
-| Route + dates, wants live pricing + bookable token | `flight_search` (see the `book-trip` skill) |
+| 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.
 
@@ -59,9 +60,33 @@ Show cheapest prices across a date range for a specific route. Great for "what's
 
 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.
 
+## price_monitoring
+
+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.
+
+**`offer_token`** in the response is re-shoppable via `flight_search` (price_check mode) when the user decides to act.
+
+**Cadence:** poll no faster than the cache refresh interval (typically a few hours). Polling faster is wasted work.
+
 ## Important notes
 
 - **Airport codes**: Use 3-letter IATA codes (PAR, NYC, JFK, CDG)
 - **Dates**: YYYY-MM-DD format
-- **Cached vs Live**: `find_destination` and `flight_calendar` use cached data — great for exploration. For live pricing + a bookable token, use `flight_search` (see the `book-trip` skill).
-- Both tools support `format: "json"` for structured output or `format: "text"` for readable summaries
+- **Cached vs Live**: `find_destination`, `flight_calendar`, and `price_monitoring` use cached data — great for exploration and tracking. For live pricing + a bookable token, use `flight_search` (see the `book-trip` skill).
+- **`price_monitoring` is cache-only** — unlike the others, it never falls back to live data. `status: "stale"` is the correct response when the cache is cold; surface it to the user instead of retrying immediately or switching to `flight_search`.
+- The tools support `format: "json"` for structured output or `format: "text"` for readable summaries

package/skills/search-hotels/SKILL.md

@@ -74,6 +74,27 @@ Two rooms with kids:
 - `total_amount` + `currency`: total price for the stay
 - `is_refundable` + `free_cancellation_until`
 
+## hotel_details
+
+Optional follow-up to `hotel_search`. Returns rich metadata for a single hotel — gallery, full facilities list, policies, per-room metadata (bed types, size, amenities, views). Use when the user wants more info on a specific result before booking.
+
+**Required params:**
+- `hotel_id`: the hotel ID from a prior `hotel_search` result
+
+**Optional params:**
+- `checkin` / `checkout`: YYYY-MM-DD. Accepted for future cache-key alignment; currently ignored by the BFF but callers are encouraged to pass them when known.
+
+**Example:**
+```json
+{
+  "hotel_id": "HID_12345",
+  "checkin": "2026-07-15",
+  "checkout": "2026-07-18"
+}
+```
+
+**Response:** `{ hotel: { id, name, description, star_rating, address, coords, images[], facilities[], policies[], checkin_time, checkout_time }, rooms?: [{ id, name, description, amenities[], bed_types[], max_occupancy, size_sqm, views[], images[] }] }`
+
 ## Booking flow
 
 Hotels use the same cart as flights — multi-domain trips supported: