Start without spending.
Your bot can help with its task without payment permission. Creating a bot or connecting an AI model does not enable payments.
BOT PAYMENTS / YOUR PERMISSION
Choose whether a bot may make payments on your behalf. Keep spending off, review each request, or allow Autopay within the limits you set.
Start with MasbotA BOT WALLET / A SEPARATE CHOICE
Yes, when you enable Autopay within limits for that bot. Payments are off by default.
Save the bot wallet’s recovery backup and confirm it before enabling spending. Choose the payment mode, review your limits and save your permission.
Autopay uses your maximum USDC amount per payment, daily USDC budget and SOL network-fee caps. Larger USDC requests ask for confirmation; fee caps still apply.
Approved bot payments are signed locally while Masbot is running and unlocked. Your current local tasks need your computer to stay on.
THREE PAYMENT MODES
Your bot can help with its task without payment permission. Creating a bot or connecting an AI model does not enable payments.
Choose Ask for confirmation when you want to review the payment request before approving it.
Let the bot pay within the budgets you save. You can change the mode and limits in its payment settings.
Bot spending is separate from what you pay for a Marketplace subscription or an AI-provider plan. See how the costs differ ↗
QUESTIONS / ANSWERED
No. Bot payment permissions control money a bot may spend on your behalf. The local app is free; optional specialist subscriptions and model-provider charges are separate.
Yes. Payments start off and can remain off. Connecting a model, creating a bot or approving an ordinary task does not enable bot spending.
No. Autopay follows the payment budgets and fee caps you save. Larger USDC payment requests ask for confirmation. Token launches and Marketplace subscription renewals have their own review and approval.
Local bot payments need Masbot running and the workspace unlocked. Hosted computers for bots are planned.