Tell Claude what you want to do onchain.
GenWallet gives Claude verified market context, safe execution, and permissioned access to your wallet, without exposing your keys.
Your wallet
MetaMask
Rabby
Phantom
Coinbase Wallet
EVM networks
Ethereum
Base
Arbitrum
Optimism
Wallet availability depends on your browser. Actions vary by network; start with Base Sepolia.
Three steps. One clear chain of control.
A useful agent needs access. It doesn’t need ownership of your wallet. Put a reviewable boundary between the two.
Give access a boundary.
Choose the networks, assets, and actions an agent can request. Set spending limits and an expiration before sharing a session.
- Network
- Budget
- Expiry
Inspect before you approve.
Check the intended action against policy, review simulation results, and see what the agent is asking your wallet to do.
- Intent
- Policy
- Simulation
Keep the final signature.
The agent submits a request, not a private key. Transactions from your EOA still need a signature in your connected wallet.
- Your wallet
- Your signature
Useful permissions. Clear limits.
Let an agent work within a budget you understand. Requests beyond that boundary need an additional approval—or stop before signing.
Separate approval from permission
An approval threshold asks for a human decision. A hard spending cap blocks the request.
Be specific about access
Limit which networks, assets, and actions a session can use.
End access when the job is done
Set an expiration or revoke a session to stop future requests.
- Ask for approval above
- $50
- Daily budget · $0 used
- $100
This amount passes the two spending checks. Your wallet signature is still required for a transaction.
Illustration only. No wallet connection, RPC call, or transaction. Real requests also undergo capability, network, intent, and simulation checks.
Start with a read. Add access deliberately.
Use the typed SDK in this repository or connect an MCP client. Keep session credentials on your server and let the wallet handle signing.
- 01Connect your wallet
Start in the GenWallet console.
- 02Create a scoped session
Choose the capabilities your agent needs.
- 03Make a read-only request
Fetch an address or balance before adding writes.
// Server-side only. Use the SDK included in this repo.
import { AgentWallet } from "@/src/agent-wallet/sdk";
const sessionToken = process.env.AGENT_WALLET_SESSION;
if (!sessionToken) throw new Error("Session token required");
const wallet = new AgentWallet({ sessionToken });
// Read-only: no transaction or signature requested.
const address = await wallet.getAddress();
const balance = await wallet.getNativeBalance(84532);
// 84532 = Base Sepolia
Uses the local SDK · Keep session tokens on your server.
Execution environment Aave supply and withdrawal default to Base Sepolia. Mainnet execution requires explicit enablement; available actions depend on the configured network and providers.
More than a Web3 MCP
MCP gives Claude tools. GenWallet gives those tools verified context, policy and safe execution.
| Capability | Free Web3 MCP | GenWallet |
|---|---|---|
| Wallet reads & transfers | Included | Included |
| Search across markets | Not included | Included |
| Verified contracts & canonical assets | Not included | Included |
| Opportunity comparison | Not included | Included |
| Persistent goal execution | Not included | Included |
| Policy, simulation & audit | Not included | Included |
Know what you’re granting.
A little clarity before you connect.
Do I need a new wallet?
No. Connect your existing supported EOA wallet. GenWallet does not ask you to hand an agent your seed phrase or private key.
Can an agent spend without my signature?
In the EOA flow, a transaction still requires your connected wallet to sign. Passing policy checks or approving a request does not replace that signature.
What happens when I revoke a session?
Revocation stops future requests through that session. It cannot undo a transaction that has already been confirmed onchain.
Does simulation guarantee a safe transaction?
No. Simulation helps inspect expected behavior before signing, but chain state can change and simulations have limitations. Always review the action, amount, recipient, and network in your wallet.
Where should I start testing?
Start with read-only calls and Base Sepolia test assets. The current Aave execution flow targets Base Sepolia by default. Do not assume every action is available on every network.
More capable agents.
The same control.
Connect your wallet, define the boundaries, and review what happens next.