LIVE · ARBITRUM SEPOLIA
Arbitrum Open House · DeFi

Give your AI agent a wallet,
not your keys.

AgentVault is an on-chain vault for AI agent treasuries on Arbitrum. The human owner sets hard spending rules in the contract; the agent's hot key can only move funds inside those rules. Deposits in, policy-bound withdrawals out, and every movement leaves a full audit trail. This page reads the deployed contract directly from the chain — no backend, nothing hardcoded.

Vault balance · live from chain
… ETH
Spent today…
Per-tx cap…
Agent status…
0x0344…d1C3 · Arbitrum Sepolia · read-only, no wallet connect
1Owner sets the policy→ 2Agent requests a spend→ 3Vault checks every rule→ 4Paid, or rejected on-chain
Live statistics
Read directly from the deployed contract — no backend, nothing hardcoded
Vault balance
ETH held by the vault right now
…
Per-tx cap
Most the agent can send in one payment
…
Daily cap
Most the agent can send per day
…
Spent today
of the daily cap used
…
Agent status
Owner can freeze the agent at any time
…
Live chain read failed — the public RPC did not answer. The values on this page are never hardcoded, so hit Refresh to retry.
Every spend passes four on-chain checks
How the policy gate works

There is no off-chain approver and no trusted server. When the agent key calls agentSpend, the contract itself enforces the policy before a single wei moves:

01Agent only
Only the registered agent key can request a spend — and only the owner can change that key.
02Allowlist
The recipient must be on the owner-managed allowlist. Strangers get nothing.
03Caps
Amount must fit the per-transaction cap and what is left of the daily cap.
04Freeze switch
If the vault is frozen, every agent spend reverts until the owner unfreezes it.
Policy lives in the contract
Rules the agent can never break
Owner-only controls. Policy, allowlist, agent key, freeze and withdrawals are owner functions. The agent key holds none of them.
Owner escape hatch. The owner can withdraw at any time, even while the vault is frozen.
Full audit trail. Every spend, policy change and freeze emits an on-chain event.
One payment passed. One was rejected on-chain.
The demo that proves it

The demo agent was given two jobs against this exact contract. The vault, not a person, decided both:

0.01 ETH
Paid to the allowlisted demo service. Inside the per-tx cap, inside the daily cap.
✓ WITHIN POLICY — EXECUTED
See the transaction on Arbiscan ↗
0.5 ETH
The agent key was valid and the vault held the funds, but the contract reverted the spend with per-tx cap exceeded. That rejection is the product.
✕ OVER THE CAP — REJECTED ON-CHAIN
On-chain identities
Who holds which key

Loading from chain…

The active spending policy
Native token policy · ETH

Loading from chain…