Setting up your agent's crypto wallet: funding, approvals, and spending policies

Every agent on Klow comes with an embedded crypto wallet. It's not a gimmick — it's how agents interact with on-chain protocols, pay for services, and execute transactions on your behalf. But you stay in control. Here's how the whole system works.

What is the agent wallet?

It's a real crypto wallet (Base network) that belongs to your agent. It can hold tokens, receive funds, and send transactions. The wallet address is visible on your agent's dashboard. Think of it like giving an employee a company card — except you get to define exactly how much they can spend and on what.

Step 1: Fund the wallet

From the Klow dashboard, go to your agent's Wallet tab. You'll see the wallet address. Send funds to it from any wallet on Base — ETH for gas, USDC or other tokens for transactions. You can also fund it directly through the dashboard if you have a connected wallet.

Check balance via Telegram

Once funded, you can ask your agent directly in Telegram: "What's your wallet balance?" It'll tell you the current balances across all tokens it holds. You can also ask it to show recent transactions.

Step 2: Choose an approval mode

This is the most important decision. Klow offers four approval modes that control how much autonomy your agent has over its wallet:

• →Watch-only — the agent can view balances and monitor positions but cannot initiate any transactions. Pure information mode.
• →Manual-approve — the agent can propose transactions, but every single one requires your explicit approval via Telegram. You see the details and tap Approve or Reject.
• →Auto-approve — transactions under a set limit execute automatically. Anything above the limit requires manual approval. Good for routine small operations.
• →Autopilot — the agent has full autonomy within configured spending limits. It executes transactions on its own judgment. Best for experienced users with well-tuned agents.

Which mode should you start with?

Start with manual-approve. Always. Get comfortable with how your agent makes decisions, what transactions it proposes, and whether its judgment aligns with yours. Once you trust it, move to auto-approve with conservative limits. Autopilot is for when you're fully confident in the agent's behavior.

Step 3: Set spending limits

Regardless of approval mode, you can set per-transaction and daily spending limits. These are hard ceilings — the agent physically cannot exceed them, even in autopilot mode. Set them on the Wallet settings page.

How the approval flow works

When your agent wants to make a transaction (in manual-approve or auto-approve over the limit), it sends you a message in Telegram with full details: what it's doing, the token and amount, estimated gas, and its reasoning. You get Approve and Reject buttons inline. Approved transactions execute within seconds.

Every transaction — approved, rejected, or auto-executed — shows up in the activity feed on the dashboard. Full audit trail, always.

Best practices

• →Start with manual-approve and small amounts. Trust is earned.
• →Set spending limits even in autopilot mode. It's a safety net, not a lack of trust.
• →Review the activity feed weekly. Know what your agent is spending and why.
• →Only fund the wallet with what the agent needs. Don't park your life savings in an agent wallet.
• →Use watch-only mode for agents that only need to monitor, not transact.

For a deeper dive into the security architecture, read Klow wallet security model explained. Looking at the bigger picture? See why your AI agent needs a crypto wallet, not a credit card.

“The wallet system is designed around one principle: your agent should be capable enough to act fast, but never able to act without your knowledge. Every transaction is logged. Every spend is bounded. You're always in control.”