Payments for software
Use native ATTO for AI agent micropayments: one API call, data request, or small digital service at a time. Atto's CLI and MCP wallet tools are available today in beta; quotes, purchase matching, and result delivery remain your application's work.
A per-call price becomes more useful when a transfer fee does not consume the payment.
Atto charges no protocol fee for sending or receiving ATTO. That makes tiny individual payments practical without grouping them just to spread a network fee. Funding, currency conversion, and running your infrastructure can still cost money.
The wallet tools accept exact decimal amounts as strings. Public node access lets software inspect accounts and transactions without operating a node; signing still requires wallet access. Payments use native ATTO, so a service must quote and accept that asset.
For a direct Atto purchase, connect the wallet transfer to your service's order flow.
The service supplies the destination, exact ATTO amount, network, expiry, and a way to associate payment with the order.
The agent checks the quote and uses its approved wallet access. Keep the request ID and returned transaction hash.
The merchant independently checks the network, destination, and amount, then binds the hash to that order and prevents reuse.
The application fulfills the purchase after verification. The recipient's separate Receive or Open transaction makes the funds spendable.
A hash supplied by a client is not proof by itself. Payment confirmation and successful delivery are separate outcomes.
Use the interface that fits your application and its permission model.
Connect an assistant over local stdio. Start read-only, then approve source accounts and spending limits yourself in a local terminal.
Use a local wallet from scripts, with structured results and durable request IDs. Review and set spending caps before granting automation access.
Connect payment actions and events with workflow credentials. Build approval and amount checks into N8N; CLI and MCP caps do not apply.
Use a dedicated wallet with limited funds, and keep its recovery phrase offline and out of agent conversations.
For CLI and MCP, review per-payment and rolling spending caps. MCP proposals require local owner approval; the assistant cannot approve itself. Payments within an approved allowance need no new terminal approval each time.
After a timeout, inspect the wallet journal. Retry the same payment with the same profile and request ID; a new ID starts another attempt. If delivery fails, retrieve the result separately before considering another payment.
Follow the recovery guide →Set up a wallet, approve an allowance, and follow the payment through confirmation.