A Paytm agent that books your flight and looks after the trip
You say where you need to be and what you can spend. It finds the best fare by a date you agree, books it, and stays with you until you're home.
Assumptions. This surface exists to bring existing users back more often. The agent uses what Paytm already knows about a user and spends only money the user blocks with their UPI PIN. In the MVP the agent has no web access and no code execution, and it calls only Paytm's own tools.
What I understand by a personal consumer agent
- An agent that does the job for you while you're out of the app.
- It knows your goals and history, works for days, and spends only what you approve.
- It's chat, search and agent agnostic, so you just say what you need.
Paytm's mission and vision
Plan and roadmap
The best experience is an always-on agent, but I'd park it and launch with pre-configured agents
why, before the plan- An always-on agent that runs any job is where this ends, and it is the long-term plan.
- Paytm moves money in a regulated space, so every rupee needs a fixed, auditable path.
- Paytm's jobs are bounded money tasks, not open-ended knowledge work.
- Booking, paying and tracking all run on Paytm's own APIs.
- The agent acts on the user's identity, so it gets the least access possible.
- It handles a UPI PIN, verified names and travel IDs.
- Browsing agents still fall for prompt injection 11% of the time.12
- A computer per user is expensive across crores of users.13
- Trust is earned one job at a time, and then the agent can widen.
A money companion for every Paytm user
what the personal agent becomes- Every user gets a private space where many agents work for them.
- All the agents share one memory of the user.
- Each agent acts only within the permissions and money the user grants.
- The user can see, pause or revoke any agent at any time.
What it takes at the scale of crores of users
inputs for the long term- A consent and permissions layer across every Paytm service.
- A shared user card that every agent reads, built in-house.
- A registry where new agents plug in without the user starting over.
- A running cost per monthly user that Paytm can carry.
Long term is what the personal agent becomes. Short term is the first job that earns the right to get there.
One agent first, built on a Paytm service
flights now- Recharge & Bills follows once the first agent earns trust.
- Travel & Tickets goes first, starting with domestic flights.
- Financial Services & Investments comes last, since money advice is regulated.
- It runs as scheduled jobs that wake on fares and flight events, not as an always-on agent.
| Memory tier | What it holds about the user | When the agent uses it | How it's built |
|---|---|---|---|
| 1 · Core profile | Name as on ID, home airport, travellers, seat and bag choices | Every turn, kept short | Paytm KYC, settings and past bookings |
| 2 · History | Every conversation and every trip | Searched only when a detail is needed | Conversation log with full-text search |
| 3 · Trip records | Tickets, invoices, boarding passes and refunds | When a trip needs them | Paytm's own document store |
| 4 · Routines | Reusable plans, like a "Diwali trip home" | When a similar trip starts | Saved after each completed trip |
| 5 · Trip notes | One-trip details, like "a 6am flight is fine this time" | Only during that trip | Deleted when the trip ends |
Adapted from Hermes Agent's tiers and the always-on agent talk.17,14,13 The shared user card joins in the long term.
| Short term · pre-configured agent | Long term · always-on agent | |
|---|---|---|
| Job | One fixed job, starting with flights | Any job the user asks for |
| Runs on | A durable workflow per trip | Its own computer per user, always running |
| Wakes on | Fare checks, flight events and the user's message | Anything, from messages to schedules to other agents |
| Tools | Paytm's own APIs only | APIs, then a browser, then a desktop |
| Model use | Only when the user talks or something changes | Most turns |
| Cost | Close to nothing between events | A computer and storage for every user |
Earnings per task come from ixigo's FY25 data, Paytm's bill fees, recharge commission rates and digital loan sizes.18,19,20,21 Effort is my judgment, so treat positions as directional.
Why I chose flights
four reasons- The ticket is big enough for a saving to matter.
- The margin leaves room to try new things.
- The agent controls the outcome, since seats are priced and not rationed.
- IRCTC, by contrast, blocks automated train booking.25
- The market already trusts agents with flights first.
- Amazon Pay and ixigo made agent-paid flight booking live in Sep 2026.26
Why not the others yet
in Paytm app orderAnkit, 27
Pune to Lucknow, 3 trips a year- He works in Pune and his family lives in Lucknow.
- He flies home three times a year, alone or with his parents.
- He pays by UPI and opens Paytm every week.
- He has never let an app spend money for him.
The moment
seven weeks before Diwali- His mother asks on the family group when he's coming home.
- He opens a travel app and sees ₹7,900 for a one-way flight.
- Last year he waited and paid even more.
| Stage | Today | Evidence | What can go wrong | Who handles it |
|---|---|---|---|---|
| 1 · Pre-booking | Sees ₹7,900 one way and feels it's too much | Festive outbound fares run 3 to 4x the return leg33 | Wrong name on ID, unrealistic budget, no mandate support | Orchestrator, Customer, Reviewer, Payments |
| 2 · Booking | Checks apps for weeks, then meets a surprise fee | 80% met fees only at the final step35 | Fares break history, fare gone at re-price, payment timeout | Scheduler, Fare Analyst, Flight, Reviewer, Payments |
| 3 · Pre-flight | Unsure about baggage, seat and check-in | 54% find choosing baggage stressful31 | Schedule change, baggage rule change, price drop | Trip, Notifier |
| 4 · Day of flight | Guesses when to leave and watches the board | 10.46 lakh passengers hit by cancellations in Dec 202536 | Delay, cancellation | Trip, Flight, Notifier |
| 5 · After landing | Waits at the belt and chases any refund | Refund complaints tripled to 4,386 in 202537 | Lost bag, stuck refund | Trip, Payments, support |
The agent books the best fare it can find by a date he agrees
a budget is a target, not a promise- The budget is the most he'll pay for the whole party, fees included.
- The agent never books above it, and the blocked amount enforces that.
- Before any money is blocked, it rates the budget as on track, tight or unlikely.
- Every watch gets a book-by date, 14 days out for domestic trips.
- Festival trips get 30 days, since fares climb earlier.
- A ticket 3 days out cost 61% more than one 22 days out.38
When fares break history
it asks him to choose- History does break, as fares crossed ₹1 lakh in December 2025.39
- The Fare Analyst works out why a route moved, and the agent passes that on.
- The agent nudges him when the odds fall or the book-by date nears.
- Each nudge offers exact choices, like booking now, another day, or a new budget.
- If he doesn't answer by the book-by date, the money is released.
Primary · UPI One Time Mandate
one per tripFallback · hold the fare, then he pays
when the mandate can't carry it- Pi holds the fare and sends a pay link when the mandate can't pay.
- His bank doesn't support the One Time Mandate yet.
- The best fare is above his budget and needs his OK.
- His bank's limit is below the fare, or he chose "just tell me".
- IndiGo's Fare Hold starts at ₹49 and lasts up to 96 hours.24
- The hold fee needs its own approval, since the mandate allows one debit.42
Trip extras · UPI Reserve Pay, once enabled
seat, bag, meal, cabOver ChatGPT and Gemini
Paytm can finish the tripOver ixigo, MakeMyTrip and Amazon Pay
a lead, not a moat- For its own users, Paytm blocks, debits and releases the money in one app.
- Checkin charges no convenience fee.53
- Flights are the first job of a money agent that later pays bills and manages credit.
North star · trips the agent books end to end
counted per finished job- A trip counts when an approved watch ends in a ticket with no dispute for 7 days.
- Intercom bills Fin the same way, per resolved conversation.56
- It doesn't hinge on the budget he first typed.
- The quality check is how often the agent beats the fare on the day he asked.
| What goes wrong | What the agent does |
|---|---|
| The budget is unrealistic | Rates it at setup and suggests a budget with a real chance |
| Fares rise past history | Nudges early with exact options, then releases the money at the book-by date |
| The fare is gone at re-price | Takes no payment and keeps watching |
| Money is taken but no ticket is issued | Retries ticketing, then refunds within RBI's 5-day limit57 |
| The airline delays or cancels | Alerts at once and offers rebooking or a refund |
| A refund gets stuck | Follows up until it lands, then hands off to support |
Appendix D lists 18 scenarios across the five stages.
Pi from the first message to landing
The screens play in order, and a label names each part as it appears. Tap a stage to jump, or pause to read. Appendix H has every screen with what runs under the hood.
Fares, dates, names, the PNR and bank details are example data.
A. Product decisions
| Solution option | User value | Feasibility | Business impact | Risk | Verdict |
|---|---|---|---|---|---|
| 1 · Fare-odds badge on the booking page | Medium | High | Medium | Low | Ship anyway, no agent needed |
| 2 · Chat wrapper over flight search | Low | High | Low | Low | Skip, it adds little over filters |
| 3 · Watch and tell, user pays | High | High | Medium | Low | Build as the default |
| 4 · Watch and book inside a blocked budget | High | Medium | High | Medium | Build for users who opt in |
| 5 · Trip agent for check-in, delays and refunds | High | Medium | Medium | Medium | Build with 3 and 4 |
Where a rule does the job, use the rule. The agent covers the timing, the trade-offs and the explanation.
One endless chat is the one thing we won't build
single chat vs multi-chat vs multi-botNo web and no code for the consumer agent
money calls for caution- In payments, the agent gets only the access the job needs.62
- The MVP has no web browsing, which shuts out prompt injection from pages.63,64
- The consumer agent has no code execution, since its toolset is small and fixed.65
- The Fare Analyst is the one exception, running code in a sandbox on fare data only.
- If an airline API fails, Pi tells the user instead of trying a browser.13
Always-on behaviour without an always-on agent
how the short-term Pi copes- Workflows can retry a step, so each money step checks status first and carries an idempotency key.66
- Each wake-up rebuilds a short trip summary, so a cold model cache costs little.67
- Routine checks run on code, and the model runs only when something changed.
- Pi speaks only when it books, the odds fall, the date nears, the flight changes or money moves.13
- The user's message reaches a running watch at once, as a workflow signal.68
- Approvals stay open until the book-by date, and silence never counts as yes.
- Each watch pins its model and prompt version and is tested on replayed fare histories.
One horizontal orchestrator over vertical agents
horizontal vs vertical- The orchestrator owns the conversation across every domain.
- Each vertical agent owns one domain and its tools.
- Multi-agent setups cost about 15x the tokens of a chat.69
Text and voice, both
conversation vs voice- The user can type or speak in English, Hindi or Hinglish.
- 14% of Paytm users already use the app in their own language.32
- The agent reads confirmations aloud, the way Soundbox does.
RAG only for airline policy pages
do we need RAG?- Fare rules arrive as structured fields from the supplier.
- Baggage and refund pages are long free text, so those go in a vector store.
B. User and agent flow
What we know about a returning user
from Paytm's own data- Saved travellers and how he books for them.
- Past trips, airlines, seats and bag choices.
- His payment methods and which bank he uses.
- Booking SMS and contacts he has allowed Paytm to read.70
What we infer for a first-time user
before asking anything- His home city from location and where he pays.
- His nearest airport from that city.
- Likely trips home from transfers to family.
- Then he answers three questions, not twenty.
Settings Pi needs for check-in
identity and rules- The traveller's name must match the ID exactly.71
- Aadhaar or DigiLocker verification confirms each traveller's name before money is blocked.
- DigiLocker links each traveller's ID for the airport.
- Airports generally accept IDs from DigiLocker's issued documents.72
- DigiYatra receives the boarding pass after web check-in.73
- DigiYatra runs at about 38 airports and is optional for domestic flights.74
- Rules show what Pi does alone and what it asks first.
- Pi watches, checks in, keeps the same seat and sends alerts on its own.
- It asks before hold fees, higher fares and name changes.
C. Agent architecture
| Sub-agent | Owns | Runs on | Tools |
|---|---|---|---|
| Orchestrator | The conversation and every hand-off | Jev + LLM | route_message, get_session, hand_off, ask_user, request_approval, summarise_context, escalate_to_human |
| Customer | Who is travelling and how they like it | LLM | get_profile, get_preferences, list_travellers, add_traveller, verify_traveller_details, get_past_trips, read_booking_sms, pick_contact, update_memory |
| Flight | Finding, forecasting, pricing and booking | LLM + XGBoost | search_flights, get_fare_history, forecast_fare, rate_budget, suggest_budget, search_nearby_dates, get_fare_rules, get_add_ons, reprice, hold_fare, create_booking, issue_ticket |
| Trip | Everything after the ticket | LLM | track_flight, open_web_checkin, select_seat, get_boarding_pass, get_baggage_rules, estimate_leave_time, rebook_flight, cancel_booking, raise_refund, track_refund |
| Notifier | Telling the user what happened | LLM | update_job_card, send_push, send_whatsapp, send_sms, read_aloud, translate_message |
| Payments | How money moves | code | list_payment_methods, check_mandate_support, create_mandate, debit_mandate, revoke_mandate, pay_by_card, send_pay_link, create_reserve_pay, debit_reserve_pay, refund_to_source, get_payment_status |
| Scheduler | Time | code | create_watch, set_book_by_date, set_timer, raise_check_rate, wake_watch, extend_watch, expire_watch, list_jobs |
| Fare Analyst | Why fares moved on each route | code, sandboxed | load_fare_history, detect_regime_break, correlate_signals, explain_move, recalibrate_odds, set_route_book_by |
| Reviewer | Checking every action before it runs | Jev + code | check_required_details, check_budget, check_fare_rules, verify_reprice, check_duplicate, score_risk, approve_reversible, request_user_approval, write_audit_log |
Every tool call carries the user's scoped session token from his Paytm login, so no agent can act outside his account, and the scope survives every hand-off.62
| Model | Use it for | Why |
|---|---|---|
| Classical ML (XGBoost) | The fare forecast and budget odds | Fares are numeric time series, and XGBoost hit R² 0.98 on Indian fares75 |
| System One (Jev) | Routing, "book now?", reviews | Typed answers with calibrated confidence in 70 to 500 ms23,76 |
| LLM (small, self-hosted) | The conversation and messages | Paytm reports its own 4B model for low cost77 |
| Reasoning LLM (frontier) | Disruptions and rebooking choices | Slow and costly, so it runs only on hard calls78 |
Why XGBoost for the forecast
what it does- It builds hundreds of small decision trees, each fixing the last one's errors.
- It reads tabular inputs like days to departure, weekday, season and seats left.
- It trains fast and shows which inputs drove each forecast.
- Deep models need far more data and are harder to explain.
How System One differs from classical ML
Jev vs XGBoost- XGBoost is trained per task on numeric features.
- Jev answers typed questions about messy text with no training.
- Both return a number, and neither writes text.
Data
what the agents readGuardrails
ask, collect and confirm- The Reviewer blocks the mandate until seven details are confirmed.
- Origin, destination, travel date and return date.
- Passenger count and each passenger's name, age and contact.
- Preferences for seat, bag and timing.
- Agents invent missing details, so the Reviewer asks instead.79
- Device binding and the UPI PIN prove it's the user.
- NPCI wants the agent to execute, never to approve.10
- SMS and messages can never change the budget or the payment.63
| Permission tier | Examples | Guardrail |
|---|---|---|
| 0 · Read | Fares, booking status, refund status, saved travellers | Scoped to the logged-in user only |
| 1 · Reversible write | Start or adjust a watch, check in, keep the same free seat, raise a refund | The Reviewer approves it inside the blocked budget, with an idempotency key |
| 2 · Money or identity | Block a budget, pay a hold fee, pay above budget, change a traveller's name | The user approves with UPI PIN or a step-up check |
| Never | Pay above the budget, move money without a PIN, promise a refund | Hard-blocked in the policy layer, not the prompt |
Grounding and hand-off
rules the model can't bend- Fares, dates and amounts come only from tool responses, and the model only phrases them.
- A tool timeout is reported plainly, never guessed.
- Repeated failure, fraud language or a request for a person moves the chat to support.
- Support gets the case summary, so the user never starts over.
| Store | Holds |
|---|---|
| Postgres | Profiles, user cards, travellers, watches, bookings, mandates, approvals and the audit log |
| Time-series table | Every fare snapshot by route and date |
| pgvector | Searchable history and airline policy pages |
| Redis | Session state, fare cache, rate limits and idempotency keys |
| Temporal | The process tracker that runs each watch for weeks66 |
| Kafka | Fare, PNR and flight-status events |
| Object store | Tickets, boarding passes and invoices |
| Feature store | Inputs for the fare model |
D. Failure scenarios
| Stage | Layer | What goes wrong | What we do |
|---|---|---|---|
| Pre-booking | Model | The LLM guesses a missing name or date | The Reviewer blocks it and the agent asks |
| Pre-booking | System | The name doesn't match the ID | Stop before booking and confirm the spelling |
| Pre-booking | System | The bank doesn't support the mandate | Fall back to a fare hold and pay link |
| Pre-booking | Product | An infant or child changes the price | Include every passenger's fee in the budget |
| Booking | Model | Jev routes a message with low confidence | Hand it to the LLM or ask the user |
| Booking | Model | The forecast misses and the fare rises | Track regret and retrain on misses |
| Booking | System | The fare changes before payment | Re-price and fail closed |
| Booking | System | Same price, worse baggage rules | Compare fare rules with the locked trip details |
| Booking | System | The payment times out | Never resend, check status, then retry once |
| Booking | System | Money is taken but no ticket is issued | Retry ticketing, then refund within 5 days57 |
| Booking | Harness | A long watch drifts or loops | Short context, step caps, resume from checkpoint67 |
| Pre-flight | Product | The fare drops after booking | Rebook inside the free-cancellation window if it saves money |
| Pre-flight | System | The airline changes the schedule | Offer the new time, another flight or a refund |
| Pre-flight | Harness | An SMS tries to change the booking | Messages can't touch budget or payment63 |
| Day of flight | System | A mass disruption hits one airline | Pause auto-booking on that airline39 |
| Day of flight | Product | The flight is cancelled | Offer the next flights and a refund in one tap |
| After landing | System | A refund is stuck with the airline | Follow up on a schedule, then hand to support |
| After landing | Harness | A bad input poisons memory | Check every memory write before saving |
E. Metrics by layer
| Layer | Metric | How it's calculated | Pilot target |
|---|---|---|---|
| End user | Trips booked end to end | Tickets from approved watches, no dispute in 7 days | 60% of approved watches |
| End user | Beat the day-one fare | Trips at or below the fare on the day he asked ÷ trips | 70% |
| End user | Regret | Fare paid minus the lowest fare seen in the window | Under ₹300 median |
| End user | Budget odds accuracy | Of budgets rated "on track", the share that booked | Above 70% |
| End user | Second watch | Users with another watch in 90 days ÷ booked users | 40% |
| Model | Router calibration | Are 80%-confident calls right 80% of the time? | Within 5 points |
| Model | Detail accuracy | Exact match on route, date and passengers | 98% |
| Harness | Consistency (pass^8) | Share of test tasks the agent gets right in all 8 repeated runs82 | Above 90% |
| Harness | Tool error rate | Failed tool calls ÷ tool calls | Under 1% |
| Latency | Speed budget | Router p95 · first reply p95 · fare change to alert · debit to ticket | 500 ms · 1.5 s · 5 min · 60 s |
| Business | Incremental bookings | Flight bookings against a 10% holdout | Positive at 95% confidence |
| Business | Margin per trip | Revenue per booking minus model, supplier and hold costs | Benchmark ₹450 on ₹6,50083 |
| Safety | Wrong bookings | Over budget, unapproved, wrong passenger or duplicate | 0 |
pass^8 asks for the same right answer eight times in a row. Top models pass all eight on retail tasks less than 25% of the time, and a booking agent has to be that consistent.82
F. Trade-offs
| Choice | We pick | We give up |
|---|---|---|
| Conversation | One thread, a context per trip | Separate personas for power users |
| Autonomy | Book alone only inside the blocked budget | Bookings above the budget without asking |
| Book-by date | Decide 14 days out, 30 for festivals | The odd late bargain |
| Payment | One ONETIME mandate per trip | Money sits blocked during the watch |
| User memory | Built in-house on Paytm's stack | A ready-made vendor like Honcho |
| Price to user | Free, while ixigo charges ₹9984 | Fee revenue |
G. Risks and roadmap
Risks
and the response- Bank support for blocked mandates varies, so the fare hold must work on day one.
- MakeMyTrip holds about 30% of domestic air tickets.85
- Amazon Pay and ixigo already let an agent pay for flights, so speed matters.26
- Domestic traffic is 0.82% below 2025, so we pitch relief from high fares.86
- Leadership ruled out standalone consumer AI, so this lives inside Paytm.87
- OpenAI pulled back its own checkout, so trust has to come from the rail.88
Roadmap
now, next, later- Now, domestic flights on top metro routes, booked 2 to 7 weeks out.
- Next, a train confirmation tracker and the cab home in the same trip.
- Later, bills and money agents once one approval covers many billers.
Payments and regulatory risks
NPCI, RBI and identity- NPCI's Unified Agent Protocol is still a draft and may require registered agents.11
- The draft builds on UPI Circle and Reserve Pay, not the One Time Mandate.11
- Paytm runs UPI through partner banks, so mandate support depends on them.
- Axis, HDFC, SBI and YES Bank have been Paytm's UPI banks since 2024.89
- RBI's authentication rules from April 2026 don't list mandate debits as exempt.90
- Paytm compliance must confirm the PIN at block creation is enough.
- The 0.4% UPI merchant fee above ₹2,000 takes about ₹27 from each flight.91
- Aadhaar checks need a UIDAI-licensed partner, so DigiLocker is the simpler first route.
H. Prototype screens
All 17 screens in order. Under each one is what woke Pi, which sub-agents ran, the memory tier it used, the tools from C.1, the permission tier and the model.
He swipes left on Paytm home, where Paytm Chat is today, and finds one agent.
- Wakes on
- Nothing until he swipes left
- Runs
- Nothing, Paytm home is unchanged
- Memory
- None
- Tools
- None
- Tier
- None
- Model
- None
- Wakes on
- Swipe left from Paytm home
- Runs
- Orchestrator
- Memory
- Core profile, from KYC and past bookings
- Tools
- get_session, get_profile
- Tier
- 0 · read
- Model
- None, the screen is code
- Wakes on
- Tap on plus
- Runs
- Orchestrator
- Memory
- None
- Tools
- list_jobs
- Tier
- 0 · read
- Model
- None
From a sentence to a blocked budget in four turns.
- Wakes on
- He opens Home chat
- Runs
- Orchestrator
- Memory
- Core profile
- Tools
- get_session
- Tier
- 0 · read
- Model
- None until he sends
- Wakes on
- His message
- Runs
- Orchestrator (Jev routes), Customer
- Memory
- Core profile gives name as on ID and home airport
- Tools
- route_message, get_profile, verify_traveller_details
- Tier
- 0 · read
- Model
- Jev routes, small LLM replies
- Wakes on
- His reply
- Runs
- Flight, Customer
- Memory
- Core profile for seat and bag, history for the last trip
- Tools
- get_fare_history, forecast_fare, rate_budget, get_past_trips
- Tier
- 0 · read
- Model
- XGBoost for odds, small LLM phrases
- Wakes on
- His reply
- Runs
- Reviewer, Payments
- Memory
- Trip notes start for this trip
- Tools
- check_required_details, check_budget, check_mandate_support, set_book_by_date
- Tier
- Card is tier 0, the next tap is tier 2
- Model
- Jev reviews, code builds the card
- Wakes on
- Tap on Book for me
- Runs
- Payments
- Memory
- None, the PIN never reaches a model
- Tools
- create_mandate (ONETIME, blockFund)
- Tier
- 2 · his UPI PIN
- Model
- None, pure code
- Wakes on
- Mandate confirmed
- Runs
- Scheduler
- Memory
- Trip notes for this trip, deleted when it ends
- Tools
- create_watch, set_timer, update_job_card
- Tier
- 1 · Reviewer approves
- Model
- None, a durable workflow starts
Weeks of quiet watching, one choice, then a ticket.
- Wakes on
- Schedule, twice a day
- Runs
- Scheduler, Flight, Notifier
- Memory
- Trip notes only, a short summary per wake-up
- Tools
- wake_watch, forecast_fare, send_push
- Tier
- 0 · read
- Model
- Code and XGBoost, the LLM writes only when odds move
- Wakes on
- Tap on the ellipsis
- Runs
- Orchestrator, Scheduler, Payments
- Memory
- Trip notes
- Tools
- list_jobs, set_timer, extend_watch, revoke_mandate, escalate_to_human
- Tier
- 1 to pause, 2 for a higher budget, cancel releases money
- Model
- None
- Wakes on
- Odds fell below fair
- Runs
- Fare Analyst, Flight
- Memory
- Trip notes store the 5 Nov change
- Tools
- detect_regime_break, explain_move, search_nearby_dates
- Tier
- ₹7,480 is above budget, so it would need tier 2
- Model
- Sandboxed code explains, Jev decides book or wait
- Wakes on
- Fare at ₹6,780 and Jev says book
- Runs
- Flight, Reviewer, Payments
- Memory
- Trip records keep the ticket and invoice
- Tools
- reprice, verify_reprice, hold_fare, debit_mandate, issue_ticket
- Tier
- 1 for the hold, the debit uses the PIN he gave
- Model
- Jev reviews, code pays
- Wakes on
- Good fare, no mandate
- Runs
- Payments, Flight
- Memory
- Trip notes
- Tools
- check_mandate_support, hold_fare, send_pay_link
- Tier
- 2 for the fee and 2 for the fare
- Model
- Small LLM phrases
The trip thread keeps working after the ticket.
- Wakes on
- Check-in opens
- Runs
- Trip
- Memory
- Core profile gives the seat, trip records keep the pass
- Tools
- open_web_checkin, select_seat, get_baggage_rules, get_boarding_pass
- Tier
- 1 · his Allow rule
- Model
- Small LLM answers
- Wakes on
- Flight status event
- Runs
- Trip, Notifier
- Memory
- Trip notes
- Tools
- track_flight, estimate_leave_time, send_push
- Tier
- 0 · read
- Model
- Reasoning LLM only if it is cancelled
- Wakes on
- Landing event
- Runs
- Trip, Notifier, Payments
- Memory
- Routines saves a Diwali trip home, trip notes are deleted
- Tools
- pick_contact, send_whatsapp, create_watch, create_mandate
- Tier
- Ask first for the message, 2 for the block
- Model
- Small LLM
Identity, rules and memory, in a sheet that rises from his avatar.
- Wakes on
- Tap on avatar
- Runs
- Customer
- Memory
- Core profile
- Tools
- list_travellers, add_traveller, verify_traveller_details
- Tier
- 2 to change a name
- Model
- None
- Wakes on
- Profile, then Rules
- Runs
- Reviewer reads these on every action
- Memory
- Core profile
- Tools
- score_risk, approve_reversible, request_user_approval
- Tier
- Never is enforced in code, not the prompt
- Model
- None
- Wakes on
- Profile, then Memory
- Runs
- Customer
- Memory
- Core profile, routines, trip records, history, trip notes
- Tools
- get_preferences, update_memory
- Tier
- 1 to edit, forgetting is instant
- Model
- None
Sources
- Paytm, About us
- YourStory, Paytm's mission, Nov 2017
- Paytm, Q1 FY27 results, Jul 2026
- Paytm, Q1 FY27 datapack
- Gartner, Machine customers will outnumber humans, 2024
- McKinsey, The agentic commerce opportunity, Oct 2025
- Razorpay, NPCI and OpenAI agentic payments pilot, Oct 2025
- Paytm, QR and Soundbox history
- Adobe, Agentic AI usage in India, Nov 2025
- MediaNama, NPCI on AI agents and UPI, Sep 2026
- Outlook Business, India plans Unified Agent Protocol for AI agent UPI payments, Sep 2026
- Anthropic, Claude for Chrome and prompt injection rates, Aug 2025
- Lee Robinson, How always-on agents work, talk on YouTube, Oct 2026
- Nous Research, Hermes Agent memory providers
- Mem0, Mem0 vs Honcho (vendor comparison)
- DEV, Honcho review, 2026
- Tina Huang, Hermes Agent Fundamentals in 29 minutes, Jul 2026
- ixigo, FY25 Data Book
- Paytm, Platform fee on bill payments, Jul 2024
- Vendor page on telco recharge commissions (unverified rates)
- IANS, Digital NBFC personal loans in FY26, Mar 2026
- Dutta and Santra, IIM Ahmedabad, dynamic pricing on Indian domestic routes, 2015
- DigitalOcean, What is Jev (TypeSafe AI), 2026
- IndiGo, 6E Fare Hold
- DT Next, Aadhaar for the first 15 minutes of booking, 2025
- MediaNama, Amazon Pay Smart Wallet lets AI agents make UPI payments, Sep 2026
- NPCI, UPI AutoPay for recharges, 2022
- Dataful, NPCI Bharat Connect monthly volumes, 2026
- RBI, E-mandate Framework for recurring transactions, Apr 2026
- Angel One, RTI data on waitlisted passengers, FY26
- YouGov, Booking burnout, India travel report 2025 (PDF, 1,019 urban Indians)
- Paytm Ads, Media Deck 2024
- ThePrint, LocalCircles on Diwali 2026 fares, Oct 2026
- Google, Track flight prices
- MediaNama, Dark patterns on airline apps, Dec 2025
- Storyboard18, DGCA data on Dec 2025 cancellations
- Tribune, Airline refund complaints, Jul 2026
- ARC and Egencia, Value of advance purchase, 2018
- Moneylife, Fares cross ₹1 lakh and emergency caps, Dec 2025
- Coey, Larsen and Platt, Discounts and Deadlines in Consumer Search, AER 2020
- Etzioni et al., To Buy or Not to Buy, KDD 2003
- NPCI OC-78, One Time Mandate block, Jan 2020
- Juspay, UPI create mandate API
- Pine Labs, UPI One Time Mandate FAQs
- NPCI OC-120, UPI limits, Sep 2021
- NPCI OC-185B, Higher limits for specific categories, Aug 2025
- NPCI OC-228, UPI Reserve Pay, Oct 2025
- PhocusWire, ixigo's ChatGPT apps, Apr 2026
- TechCrunch, Google AI Mode travel, Aug 2026
- Amadeus, Paytm partnership, Nov 2023
- PhocusWire, Sabre agentic APIs, Sep 2025
- Outlook Business, UPI app market share, 2026
- TravTalk, Paytm Checkin zero convenience fees, Nov 2025
- Paytm, Q4 FY26 earnings call takeaways, May 2026
- MediaNama, Paytm on agentic AI, May 2026
- Intercom, Fin resolutions
- RBI, Turn-around time for failed transactions, Sep 2019
- Chroma, Context Rot, Jul 2025
- NoLiMa, ICML 2025
- Anthropic, Claude memory and projects
- Meta, AI in chats and reset commands
- Juspay, Building a payment intelligence agent enterprises can trust
- OWASP, LLM01 Prompt injection
- Simon Willison, The lethal trifecta, Jun 2025
- Wang et al., CodeAct, ICML 2024
- Temporal, OpenAI Agents SDK integration
- Anthropic, Effective context engineering, Sep 2025
- Temporal, Workflow message passing (signals)
- Anthropic, Multi-agent research system, Jun 2025
- Paytm, Privacy policy, Jul 2024
- Air India, Documents to carry
- HappyFares, Documents for domestic flights in India (secondary)
- HappyFares, DigiYatra guide 2026 (secondary)
- SuperKalam digest, DigiYatra at 38 airports, Jun 2026
- Airline ticket price prediction with ensemble ML, 2025
- Deußer et al., Benchmarking the System One model Jev, Sep 2026
- MediaNama, Paytm Intelligence, Sep 2026
- From System 1 to System 2, a survey of reasoning LLMs, 2025
- Learning to ask when LLM agents meet unclear instructions, EMNLP 2025
- Langfuse, Sessions
- OpenAI, Agents SDK guardrails and approvals
- Yao et al., τ-bench, 2024
- MakeMyTrip, FY26 annual report (20-F)
- ixigo, Smart Lock
- MakeMyTrip, Q3 FY26 earnings call, Jan 2026
- Free Press Journal, DGCA traffic for Sep 2026
- Inc42, Paytm on enterprise AI, Jul 2026
- Skift, OpenAI walks back ChatGPT checkout, Mar 2026
- ThePrint, Paytm moves UPI users to Axis, HDFC, SBI and YES Bank as a TPAP, Apr 2024
- RBI, Authentication mechanisms for digital payment transactions, Sep 2025
- Angel One, 0.4% UPI merchant fee above ₹2,000, Sep 2026