Start login: ask the eSIM platform to send a six-digit one-time code to the user's email address or phone number. WHEN: the user wants to log in or sign in, or something you are about to do needs a signed-in user and get_login_status reports nobody is signed in. FIRST: ask the user which email address or phone number to use if they have not said yet. Pass exactly one of them, exactly as the user gave it. Never invent, guess or auto-complete an address or number. AFTER SUCCESS: tell the user that a code was sent to the masked destination in the result and ask them to read out the six-digit code, then call verify_login_otp. The user is NOT logged in yet -- do not say login is complete. DO NOT call this tool again for the same login attempt; it is rate limited. If the user says the code never arrived, use resend_login_otp.

Send the pending one-time code again, to the same destination as the login already in progress. WHEN: only when the user explicitly asks for another code ("resend it", "I never got it"). Pass the same email or phone that started the login. DO NOT call this on your own after a wrong or expired code, and do not use it to retry a failed request_login_otp. If the platform reports that a code is still active or that the limit was reached, tell the user plainly and wait -- do not call it again.

Finish login: verify the six-digit code the user received and open their eSIM session. WHEN: the user has given you a six-digit code for a login you started with request_login_otp. Pass that code together with the same email or phone the code was sent to. AFTER SUCCESS (status 'authenticated'): tell the user they are signed in. The session is kept on this server for this client; you never see, need or handle any token. DO NOT ask the user for an access token, a refresh token or a password, and do not retry a rejected code by yourself -- ask the user to re-read it, or to ask for a new one.

Check whether this client already has a signed-in eSIM user. Local and fast: it does not call the eSIM platform. WHEN: before anything that needs a signed-in user, and whenever the user asks whether they are logged in. If 'authenticated' is true, carry on -- do not ask the user to log in again. If the result shows a pending login, ask the user for the six-digit code instead of starting a new login.

Read the signed-in user's own profile and wallet balance from the eSIM platform. WHEN: the user asks about their account, profile, name or balance -- and only while they are signed in. If this answers 'authentication_required', start the login flow with request_login_otp instead of asking the user for any credential. Contact details come back masked; tokens and internal session data are never included, so do not ask for or expect them. PRIVACY: repeat the masked email and phone exactly as returned. Never restore or retype the complete address or number, not even when the user typed it earlier in this conversation -- say 'your email' or the masked form instead.

Sign the current user out of the eSIM platform, for this client only. WHEN: only when the user explicitly asks to log out or sign out. DO NOT log anyone out on your own -- not after an error, not to 'reset' things, not at the end of a conversation. Other clients and other users are unaffected.

List the countries the eSIM platform sells plans for, or check the one the user named. WHEN: the user asks which destinations are available, or you want to confirm a country exists before searching for plans. Pass the user's own wording as 'query' to resolve it; omit 'query' to browse. The result is deliberately a limited extract plus a total count -- do not read the whole list out, ask the user where they are travelling. This needs no login.

List the regions the eSIM platform sells multi-country plans for, such as Europe. WHEN: the user mentions a region, asks what regional plans exist, or is travelling to several countries in one area. Use a region from this result with find_bundles_by_region. This needs no login.

Show what the catalogue offers: how many destinations and regions exist, plus a few cruise and global plans. WHEN: the user asks something broad like "show me all bundles", "what do you have" or "what plans are there". IMPORTANT: there is no endpoint that returns every plan for every country, so never claim to be showing all of them. Use this overview to say what kinds of plans exist, then ask which country or region the user is travelling to, or whether they want a global or cruise plan. This needs no login.

Find the eSIM plans available for one country. WHEN: the user names a destination country -- "I need an eSIM for France". Pass the country exactly as the user said it (name, ISO2 or ISO3); this tool resolves it against the platform's own list. Only pass a filter the user actually stated (budget, minimum data, minimum validity, unlimited). AFTER SUCCESS: present a few options as a numbered list with data, validity and price, and ask whether the user wants details on one of them. Keep the bundle_code of each option so that "the second one" can be looked up with get_bundle_details; never read a code out to the user and never invent one. The result covers this destination only -- never describe it as the platform's whole catalogue. Prices are catalogue prices and may not include final tax. This needs no login; browsing must never be blocked behind signing in.

Find the multi-country eSIM plans available for one region, such as Europe. WHEN: the user names a region, or is visiting several countries in the same area. Pass the region as the user said it (name or code); this tool resolves it against the platform's own region list. Filters and presentation work exactly as in find_bundles_by_country: only pass filters the user stated, then offer a short numbered list and keep each bundle_code for follow-up. The result covers this region only. This needs no login.

List the eSIM plans sold for cruise ships. WHEN: the user says they are going on a cruise, names a ship or a cruise line, or asks for maritime coverage. Each plan covers specific ships; the summary carries how many, and get_bundle_details names them. If the user has a particular ship in mind, check it there before promising coverage. This needs no login.

Read the full details of one plan: data, validity, price, coverage, plan type, activation policy and availability. WHEN: the user asks about a specific plan you already listed -- "tell me more about the second one". Pass the bundle_code of the option the user picked, taken from the result you already have. Never invent a code, and never ask the user to read one out. AFTER SUCCESS: describe the plan in ordinary language and pass on the price note: the displayed catalogue price may not include final tax. Nothing here reserves, orders or charges anything -- this version cannot buy a plan. This needs no login.

Prepare a signed-in user's chosen plan for buying, and report exactly what it would cost. This does NOT buy anything: it creates no order, moves no money, and reserves nothing. WHEN: a signed-in user has picked a real plan from a list you showed and wants to go ahead -- "I want the second one", "prepare the cheapest France plan". FIRST: the user must be signed in. Check get_login_status and run the normal login conversation if they are not. Then ask whether they want to use their wallet balance or a card, and pass their answer -- never pick for them. Pass the bundle_code of the plan they chose, taken from the catalogue result you already have. Never invent a code and never ask the user for one. If it is unclear which plan they mean, ask them which one before calling this. The plan's price, availability and the wallet balance are all re-read from the platform here, so you cannot supply them and must not assume them. AFTER SUCCESS: tell the user the plan, the amount and the payment method, and say plainly that no order was created and nothing was charged. Never say the plan is reserved, held or bought. Do not ask for card details. Do not call this again for the same choice -- if you do, the earlier quote is replaced. Preparing is not paying, and this tool cannot take a payment of either kind. Only once the user has heard the amount and explicitly agreed to it does paying begin: confirm_purchase for a Wallet quote, create_card_checkout for a Card quote. Never start either on your own initiative.

Read back a quote you prepared earlier in this conversation: the plan, the amount, the payment method and whether it is still valid. WHEN: the user asks about what you prepared -- "show me my prepared purchase", "what was that going to cost". Pass the quote reference from the prepare_purchase result. This reads local state only and never contacts the eSIM platform, so it changes nothing. A quote is short-lived. If the result says it expired or was cancelled, say so plainly and offer to prepare the plan again -- and repeat that no order was created and nothing was charged.

Throw away a quote you prepared earlier. This discards local information only. WHEN: the user says they do not want the plan you prepared, or wants to start again. IMPORTANT: there is no order behind a prepared quote, so nothing is cancelled at the eSIM platform and nothing is refunded or reversed -- there was never a charge. Tell the user the prepared quote was discarded; never tell them an order was cancelled. This never contacts the eSIM platform.

Buy the plan in a quote you prepared earlier, paying from the user's eSIM wallet. THIS SPENDS REAL MONEY: it creates an order at the eSIM platform and debits the wallet balance. It cannot be undone from here, and there is no refund tool. WHEN: only after the user has been told the plan, the exact amount and the payment method, and has explicitly said yes to that amount -- "yes, buy it", "confirm", "go ahead". Never call this on your own initiative, never to "check" something, and never because the user merely asked to prepare or price a plan. Wanting a quote is not agreeing to be charged. FIRST: prepare the plan with prepare_purchase, read the amount back to the user, and wait for their answer. If the quote has expired, prepare it again and get their agreement to the new amount -- never confirm an amount they have not heard. Pass only the quote reference from your own prepare_purchase result. The plan, the price, the currency and the payment method come from that stored quote, so you cannot supply or change any of them here. Wallet only in this version. A quote prepared for card payment cannot be bought. SAFE TO REPEAT: calling this twice with the same quote reference returns the stored result of the first purchase and never buys the plan twice. AFTER SUCCESS: tell the user plainly that the plan was bought and paid for from their wallet, with the plan name and the amount. IF THE RESULT IS UNCLEAR: if the outcome is reported as unknown or as needing support, never say the purchase succeeded and never say it failed. Do not prepare a new quote for the same plan and do not try to buy it again -- say the platform is confirming it, and offer to check the same purchase again.

Open the eSIM platform's secure hosted checkout page for a plan the user prepared for card payment, and return the payment link. THIS CHARGES NOTHING BY ITSELF: it creates a payment page, and the user pays on that page or does not. WHEN: only after the user has been told the plan, the exact amount and the payment method, and has explicitly said yes to paying that amount by card -- "yes, pay by card", "open the payment page", "go ahead". Never call this on your own initiative, and never because the user merely asked to prepare or price a plan. Wanting a quote is not agreeing to pay. FIRST: the user must be signed in, and the plan must already be prepared with prepare_purchase for 'Card'. Read the amount back to them and wait for their answer. If the quote has expired, prepare it again and get their agreement to the new amount -- never start a payment for an amount they have not heard. Pass only the quote reference from your own prepare_purchase result. The plan, the price, the currency and the payment method come from that stored quote, so you cannot supply or change any of them here. NEVER ask the user for a card number, an expiry date, a security code, a cardholder name or any other card detail, and never offer to enter one for them. Card details are entered only on Stripe's own secure hosted page, which the returned link opens in the user's own browser. This server never sees a card. SAFE TO REPEAT: calling this twice for the same prepared quote returns the same payment link and never opens a second page, so the user is never asked to pay twice. AFTER SUCCESS: give the user the link, the plan and the amount, and say plainly that nothing has been charged yet. Then wait -- do not check the payment until they say they have paid or ask you to check, and use check_card_payment_status when they do.

Ask the eSIM platform what happened to a card payment you started with create_card_checkout. This is the ONLY way to know whether a card payment went through: the platform's own payment webhook confirms the payment and sets up the eSIM, and this tool reads the result of that. Nothing here can make a payment succeed. WHEN: the user says they have paid, or asks you to check. Do not call it on a loop and do not keep checking on your own -- one check per request, and only when there is a reason to. NEVER treat any of these as proof of payment: the user returning to this conversation, a browser redirect, a success screen on the payment page, or the user simply saying it worked. Only this tool's answer counts, and there is no argument here through which you could tell it that a payment succeeded. The answer means exactly what it says:

• not paid yet: give the user the link again and wait; do not ask for card details.

• payment received: the money arrived but the eSIM is not ready -- never say the plan is active, installed or activated; offer to check again in a minute.

• complete: the plan was paid for by card and the order is done. Tell the user plainly, with the plan name and the amount.

• failed, expired or cancelled: nothing was charged. Say so plainly and offer to prepare the plan again and open a new payment page. IF THE RESULT IS UNCLEAR: if the payment is reported as unresolved or as needing support, never say it succeeded and never say it failed. Do not check it again, do not open another payment page and do not prepare another quote for the same plan -- tell the user the platform is investigating it and that they should contact eSIM support.