Payments & safety
Updated:
Confirmation
Every action that changes your account or spends money is confirmed with you before it runs. Price previews (calc_*) are shown before orders and renewals. Most clients additionally ask you to approve each tool call.
Warning: order, renewal, top-up and other write actions have no idempotency — repeating a confirmed request repeats the action (a second order, a second charge).
Note: clients with a chat memory (ChatGPT's “Use memory”, for example) can let the assistant fill in answers it would otherwise ask you for — the purpose of a purchase, a payment source, even a confirmation — from earlier chats, and such clients may show fewer of their own tool-approval dialogs. With memory off the assistant follows the rules strictly and asks every time. If you want to be asked, turn memory off for this connector or state your choices explicitly in each request.
Payment sources
There is no default payment source; the assistant asks how you want to pay.
Action | Accepted payment |
|---|---|
Account balance ( | |
Account balance or a method from list_payments accepted for renewals | |
Account balance or connected card | |
External method from list_payments (PayPal, card, crypto…) — a linked card is charged at once, other methods return a payment link | |
Card bound in the Proxy-Seller dashboard |
PayPal, crypto and one-off card payments need a browser redirect, so they cannot pay for an order directly from the chat. Top up the balance with add_balance first, then order from the balance.
Note: after an order or renewal succeeds, the money has already been charged. There is no payment link in the response.
Note: add_balance with a linked card is charged immediately — the returned link is only a thank-you page and does not have to be opened. With PayPal, crypto or a card that is not linked the top-up completes only after you open the link and pay. Either way, ask the assistant to check the balance afterwards, and do not repeat the request just because the link was not opened.
Recurring charges
Auto-renewal keeps proxies active and pays for each renewal. With the balance as the source, funds must be there by the charge date, which can be a day before expiry. If the balance is too low, auto-renewal still turns on and you get a warning.
Auto top-up keeps money on the balance by charging the bound card at a threshold.
Both can be turned off with only
account:write. Turning them on needsbilling:write.
Keep your account safe
Grant
billing:writeonly to clients you trust to spend money.Proxy passwords reach your AI provider only when you ask for them — Proxy passwords and the AI provider.
Do not paste your Client API key into a chat — the MCP server never needs it.
Revoke access by removing the server from the client.
Proxy passwords and the AI provider
Everything a tool returns becomes part of your conversation with the assistant, and the conversation is processed by the AI provider that runs the model (Anthropic, OpenAI, or whoever hosts it). Depending on that provider's policy it may be retained in chat history or logs. The MCP server cannot control what happens there, so it minimises what gets there in the first place:
Masked by default.
list_proxies,list_auth,list_resident_lists,list_resident_subuser_listsreturnpasswordas“••••”, andexport_proxiesreturnsip:portlines. Most questions (what is expiring, how much traffic was used, which authorizations exist) are answered without a single password leaving Proxy-Seller.Revealed on request only. The same tools take
reveal: true. The assistant is instructed to use it only when you ask for the credentials. An explicit request — “show me the logins and passwords of my residential lists”, “export as csv with passwords” — counts as that confirmation, and the assistant does not ask a second time; an ambiguous one (“export my proxies”) gets the password-free form and an offer to reveal. Treat such a request like a purchase confirmation. Tools whose purpose is to hand you newly generated credentials (add_auth,create_resident_tools_list,create_resident_subuser_tools_list) return them in clear.You are told every time. Any result that contains passwords in clear carries a Sensitive data warning, and the assistant is instructed to repeat it: the credentials are now part of this conversation, are sent to the AI provider, and may remain in the chat history and the provider's logs. If that is a concern, rotate them (next point).
Not logged here. The MCP server does not log tool arguments or results; it records only per-tool call counts and latency. Its log lines pass through key-based redaction, and HTTP client logging is capped so the upstream URL, which carries your Client API key, never reaches a log.
If credentials were exposed, rotate them. Ask the assistant to change the password (
change_authwith a newlogin/password), or delete and recreate the authorization (delete_auth+add_auth). Residential list credentials are regenerated by deleting and recreating the list. Active proxies pick up the new credentials immediately.Choose the provider deliberately. If your policy does not allow proxy credentials at a given AI provider, connect that client with
docs:readonly, or withaccount:readand an instruction never to reveal.