PLANET × EaseMyTrip

What you're looking at

The phone on the left is the PLANET app, exactly as a customer would use it. The panel on the right shows the work happening behind the scenes with EaseMyTrip, as it happens. Every booking here is a real booking on EaseMyTrip's test system — real ticket numbers (PNRs), but test flights and no real money. Nothing is pre-recorded.

What the customer can do

Book in one chat: tell KAI where and when, pick a flight, share passenger details, pay by UPI — done, ticket issued. Or set a price and walk away: tell KAI "book under ₹5,000", approve payment once, and KAI keeps checking fares on its own — the moment a fare is right, it books. The customer never has to come back and approve again. And they can simply speak — tap the mic, say it, and KAI transcribes and acts on it live.

Reading the right panel

Blue lines are KAI thinking out loud — what it understood, what it decided, what it will do next. Dark cards are the actual exchanges with EaseMyTrip: finding flights, confirming the latest price, making the booking, checking the ticket. Tap any card to see the full detail.

The price watch, honestly shown

When a customer sets a target price, KAI checks fares again and again — in real life about once an hour, since airline fares typically move every two to three hours. The demo squeezes days into seconds, so you'll see those repeated checks happen live in the panel.

When things change mid-booking

Flight seats sell out and prices move — sometimes in the seconds between choosing and paying. When that happens, KAI notices, quietly re-checks the flights and completes the booking another way. And if a fare rises at the last moment, the booking simply doesn't go through — no extra money is ever taken.

What's ready, what's coming

Ready now: the full flight journey — instant booking, the price watch, and live ticket status — running against EaseMyTrip's test system. Coming: real payment settlement (UPI here is a demo), cancellations, buses and hotels — these depend on items EaseMyTrip is enabling for us. Download logs saves a complete record of any test run, useful for sharing proof of what happened.

For the technical team (Pine Labs) — this demo is the working spec

Everything below is already running here; expand any card in the panel or use Download logs to get the exact request/response for each step. Build to what you see — there is no separate PRD.

Booking sequence: FlightSearch → AirRePrice → (SSR add-ons, optional — skip) → AirBook → GetBooking. One transaction = one TraceId, carried unchanged from Search through Book. The customer pays the repriced fare — Reprice's total is what goes into AirBook as the booking amount.
Commercials: per-adult fare, commission and TDS are read from the Reprice response (net payable = fare − commission + TDS). Offer/discount fields appear in the same fare object once EaseMyTrip maps the agency ID.
Sold out mid-transaction (error 019 at Reprice / B14 at Book): the fare class is gone, not the flight. Recovery, as agreed with EaseMyTrip: re-run FlightSearch, then Reprice + Book from the fresh listing (new TraceId). If the same flight still fails, fall through to the next candidate fare.
Fare increase at Book: surfaces as an error in the AirBook response; the booking does not complete. Never debit beyond the amount the customer approved — re-confirm or refund.
Status: no webhooks yet — poll GetBooking by transaction id (booking status, ticket numbers, refundability). For price watches: fares refresh roughly every 2–3 hours, so poll each watched route about hourly.
Passenger rules: 10-digit Indian mobile (starts 6–9), sent with country code 91; title drives gender; email receives the e-ticket.
Payments: this demo simulates UPI collect + one-time mandate. Production model under confirmation with EaseMyTrip: the PG collects from the customer and settles to EaseMyTrip as merchant of record — no agency wallet pre-funding.
Credentials: EaseMyTrip credentials live server-side only — never in the app or the browser. Production switch is the base URL plus the production agency ID; the request shapes stay the same.