Availability and limits
Who can connect, what a purchase can be, and the request limits the service enforces.
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. Envoy decides for each purchase who checks out. The agent can pay with a one-time card, for ₹10 to ₹10,000, or Envoy checks out itself. Eligible purchases can use a gift card. Follow its returned funding task; see the gift-card guide. Totals above ₹10,000, up to ₹1,00,000, go to Envoy checkout. Envoy is available in India only. The user needs an existing Envoy account. The user completes KYC in the Envoy app, and it can limit what the user can do. The limits below are the ones the service enforces.
Support revision: envoy@2026-10. Last updated: 3 November 2026. A revision label is not proof of what a given host has verified; see Connect your assistant.
Who can connect
- An existing account. The user signs in on Envoy's first-party page and approves the agent's connection. Envoy can send a sign-in request to the app or an SMS code. A browser agent may enter the SMS code once, only on Envoy's page, after the user reads it aloud. The agent must never store, log or repeat the code. If the host forbids entering a sign-in code, use the Envoy app request. If that is unavailable, stop. See the browser agent guide. With remote MCP, the user completes sign-in in the host's window; see Connect your assistant.
- The purchase service enabled for that user and client. If it is not, the HTTP API returns
SERVICE_NOT_ENABLED(REST only). Over MCP the briefing tells you to stop. Stop and tell the user. - A host that supports remote MCP with OAuth, or your own HTTP client. Host-by-host status is in Connect your assistant.
A successful sign-in does not prove the account can pay. KYC happens only in the Envoy app; see KYC and eligibility.
There is no test mode. Every purchase moves real money.
What a purchase can be
| Rule | Value |
|---|---|
| Currency | INR |
| How Envoy pays | Envoy chooses the route. The agent can use a one-time card or paid gift-card voucher, or Envoy checks out itself. checkout_by says which. Totals above ₹10,000 go to Envoy checkout, which needs address or address_id in start_purchase. Connections Envoy identifies as ChatGPT or Claude connectors use Envoy checkout and omit report_checkout_result and report_checkout_step. They receive no card details or checkout codes. Other clients use their returned catalog and route. The one-time card range does not limit operated checkout. |
| Card limit | ₹10 to ₹10,000 per one-time card (at most one card per purchase). On the one-time card route, a total below ₹10 fails, and nothing is created. |
| Highest total | ₹1,00,000 for one purchase, the most the user's connection consent allows. Above it, start_purchase fails with INVALID_INPUT, and nothing is created. |
| KYC | Completed by the user in the Envoy app. See KYC and eligibility. |
| Purchases at once | Up to five open purchases per user. A second open purchase from the same agent at the same merchant for the same amount is refused. Envoy also refuses a second Envoy-checkout or at-checkout purchase on a site where the user already has an open purchase, at any amount, and allows at most three approvals waiting on the user at once. Any of these refusals is ACTIVE_PURCHASE_EXISTS on the HTTP API (REST only); over MCP the briefing tells you to stop. |
| User authorization | Follow the returned task: approval or payment in the Envoy app, or a gift-card payment link the user pays themselves. |
| Bank verification | On agent card checkout, the returned checkout_code is the card's bank OTP. On Envoy checkout, the user enters any bank OTP in the Envoy app. No Envoy tool accepts a bank or payment OTP. |
The card limit applies to each one-time card, not to a day. Do not split a larger total across purchases. Account balances and limits come from get_account; a missing value means unknown, not unlimited. The payment walkthrough explains the card in full.
Envoy does not read SMS. A failed payment does not prove that money returned. Read the returned money status and contact support if the outcome stays unclear. Merchant refunds follow the merchant's policy. When checkout_by is agent, the agent owns the merchant session. When it is envoy, Envoy places the order. The user owns merchant sign-in answers and bank verification on Envoy checkout. At the agent's bank step, use only the one-time card's returned checkout code. See Before you start and Credentials.
Need a higher limit?
The per-purchase card limit (₹10,000) is separate from account balance limits. Balance limits depend on KYC; completing video KYC raises the balance limit. See KYC and eligibility. For anything else, ask support at envoy.money/support or support@envoy.money.
Request limits
| Surface | Limit |
|---|---|
Tool calls, /tools and /mcp together | 120 per minute per access token; over it, RATE_LIMITED |
| Failed authentication | 600 per minute per client IP |
POST /installation/challenge | 60 per minute per client IP; each challenge lasts 60 seconds and is used once |
| JSON body | 64 KB |
list_transactions page | limit 1 to 50 |
list_purchases | limit 1 to 20, newest first |
Held get_purchase_status | Up to next.args.wait_seconds; the server may hold less |
Respect next.after_seconds before any retry. Do not rotate connections to get around a limit. The authorization server sets its own limits for sign-in and token calls.