Data and permissions
What an Envoy connection lets an assistant read or change, and which records Envoy keeps.
Connecting lets this assistant read your Envoy account and request purchases. The user completes the returned approval or payment step in the Envoy app. If Envoy returns a gift-card payment link, the user pays that link themselves. Follow the returned user task. Review Envoy's Privacy Policy and Terms before connecting.
Support revision: envoy@2026-10. Last updated: 3 November 2026. The connected server's tool list and the consent screen show the current permissions.
What the tools can do
| Tool | Access | What the assistant receives or changes |
|---|---|---|
get_account | Read | Balance, limits, services and an active purchase. The assistant can also request profile fields (name, verified mobile number and email) and saved delivery addresses when available. |
list_transactions | Read | Transaction history for the connected account. |
list_purchases | Read | Purchases made through this agent, newest first, as Envoy last stored them. No card details. |
get_purchase_status | Read | A purchase's state. An authorized ready reply can release this purchase's card details and checkout code, or a paid gift card's code and PIN. Follow next; ready status can also start Envoy's gift-card checkout. |
start_purchase | Change | Requests a purchase for the merchant and amount the user specified. The user completes the returned approval or payment-link task. |
answer_purchase_question (deprecated name submit_answer) | Change | Sends the user's answer to an open purchase question, or optional feedback. An exact otp question can ask for a merchant or Instinct vault sign-in code. Envoy does not ask for a password. |
report_checkout_result | Change | Reports paid on merchant confirmation or failed with a reason. If the outcome is unclear, use failure_reason: other. A report does not prove the card is closed or payment settled. |
report_checkout_step | Change | Shows a reached step of an agent checkout in the Envoy app. Moves no money, returns no card and is safe to repeat. |
cancel_purchase | Change | Requests a stop. After a report, cancellation needs a reopened ready card. Gift-card issuance can make cancellation unavailable. Follow the reply. A merchant order is separate. |
list_gift_card_merchants (deprecated name get_merchants) | Read | Lists gift-card merchants, supported amounts or ranges, redemption location when known, and any maximum advertised discount. |
search_products | Read | Returns marketplace offers when available, with their current prices and expiry. It moves no money. |
This table describes the default profile. A connection Envoy identifies as Claude uses Envoy checkout, lists nine tools and omits report_checkout_result, report_checkout_step and the deprecated names. One identified as ChatGPT lists eight, also omits list_gift_card_merchants, and buys only from Elixir's marketplace. Neither receives card details or checkout codes. Other clients use their returned catalog and route.
The account owner signs in and approves the connection on Envoy's first-party page. The assistant does not receive that sign-in OTP. The user completes the task returned for each purchase. Connection and discovery explains the host-specific tool catalog and how to disconnect.
Where the data goes
Envoy receives the inputs you send to its tools and reads account and purchase facts from the services that own them. Envoy stores connection, session and installation records so it can authorize and revoke access. It stores purchase request and audit references to make retries and recovery safe. The purchase service owns purchase execution and financial state. Envoy's authorization service owns the live connection grant and consent record.
Envoy's operational tool events use bounded status fields and pseudonymous references. They do not log raw tool inputs or outputs, card details, passwords or OTPs. Operational records and purchase audit records are separate. This page does not set a retention period; consult the Privacy Policy for the applicable policy.
An authorized ready reply can carry a one-time card or a paid gift-card voucher for that purchase. A merchant or Instinct vault sign-in code can pass through submit_answer only for Envoy's exact open otp question. On agent checkout, the card's checkout code is its bank OTP, entered once on the bank page; the bank sends the user no code for that card. On Envoy checkout, the user enters any bank OTP in the Envoy app. Keep card details, voucher codes, PINs and sign-in codes out of agent replies, files and feedback. Your assistant host may retain tool history; review its settings before you make a purchase. See Credentials for the different card, sign-in and bank-code paths.
Why sign-in may show another domain
Envoy's OAuth issuer is gateway.joinelixir.club. Its metadata names auth.envoy.money as the authorization page, where the user signs in. The issuer handles token, registration and revocation calls on gateway.joinelixir.club. The MCP tools remain at api.envoy.money. Follow the endpoints advertised by Envoy's OAuth metadata.