Live on BOT Chain testnet 968

Give your AI agent a wallet it can’t drain.

BOTSpend doesn’t make agents smarter. It makes them safe to fund — the agent holds nothing, a sponsor policy fences it to the vault at the gas layer, and the vault enforces caps, allowlists and receipts on-chain.

The problem

One bad loop and the wallet is empty.

Autonomous agents need to move money to act — pay a vendor, settle a task, swap on a DEX. Hand one an unrestricted key and a single prompt injection, hallucinated action, or runaway loop can drain it.

Humans need caps, allowlists, dedup and receipts — enforced on-chain, not by app-layer goodwill. BOTSpend gives the agent a wallet that holds nothing and can only ever move value inside policy.

The architecture

Two independent fences.

Neither substitutes the other. One stops off-policy actions from ever broadcasting; the other polices every spend that does.

Fence 1
Gas layer · BOT Chain native

It can’t even broadcast

The agent’s account holds zero BOT. Every action is a sponsored UserOp, and the paymaster’s off-chain signer only signs calls into the vault. An off-policy action is never sponsored — with no gas, it never enters a bundle.

Fence 2
Contract layer · the vault

It only moves inside policy

For any call that does get sponsored, the vault checks the full policy — active, not expired, token allowed, target allowed, per-tx cap, daily cap, dedup — before moving a cent. Blocked actions emit an on-chain record and move nothing.

How it works

Fund the vault. Fence the agent.

01

The agent holds nothing

No BOT, no stablecoin, no gas. The agent is just a smart account whose key can sign — but a signature alone moves nothing and pays for nothing.

02

The sponsor pays — only for vault calls

The agent submits a gasless UserOp. A sponsor policy signs it only if the call targets the vault. Anything off-scope gets no signature, no gas, no inclusion.

03

The vault enforces, then receipts

Inside the vault, the spend is checked against caps, allowlists and dedup. Approved moves value and emits a receipt; blocked emits a record and moves nothing.

Live proof · on-chain

Same agent. One variable.

Two real sponsored actions from agent 0xCc19…fa2B, identical but for the amount — 4 mUSD vs 6 mUSD against a 5 mUSD per-tx cap. The difference lives entirely in the events and the untouched balances.

executeSpend
Event
Resultnothing moved
Transaction
vs
executeSpend
Event
Resultnothing moved
Transaction

A wallet your agent can’t drain.

Watch the policy, the sponsor status and every approved and blocked action — live from the deployed contracts on BOT Chain 968.