# A wallet for each agent: its balance is the worst case

URL: https://www.orla.finance/en/product/crypto/agent-wallet
Markdown twin of that page. Append `.md` to any Orla page URL to get one.

An agent pays for data and services by x402 from a wallet whose balance is its whole budget. Every payment has a receipt: which agent, whose money, to whom and who decided.

## How it works

- **The balance is the budget.** You fund the wallet, and it can never spend more than it holds. What is left comes back out whenever you ask, with your second factor.
- **Two ceilings and a list.** A ceiling per request, a ceiling per day and the hosts it may pay. A purchase past either is refused on the spot, and an empty list pays nobody. A transfer past the day waits in your queue.
- **An address pinned.** The first payment to a host pins where it was paid. A host that asks for another address is refused until an owner confirms it against the host's own documentation.
- **A card is its own fence.** An agent can hold a card as well. The balance loaded on it is its whole limit, and freezing the agent stops the card too.

## Questions

**What is the worst case if an agent goes wrong?** What its wallet and its card hold. It cannot pay from your accounts, where anything it wants is only a proposal, and a host cannot quietly change where it is paid.

**How do I choose what it may buy?** Find a service searches catalogues of x402 sellers by what they do. One press of Allow opens that host to the agent and files it as a supplier, with an optional monthly cap.