A planned crypto wallet for AI agents.
BroWallet is in development. Receiving, swapping, and sending assets and gas abstraction are planned, but production access is not yet available.
"status": "PREVIEW_ONLY",
"gasAbstraction": "PLANNED",
"capabilities": ["planned_deposit", "planned_swap", "planned_withdrawal"]
A planned wallet model for AI agents.
The concept below covers MPC controls, balances, swaps, payments, and statuses; these capabilities are not yet available in production.
Agent is the primary client
A machine-facing interface for wallet creation and financial operations from agent workflows is planned.
No native gas token required
Network-fee abstraction is being considered as a future capability; supported networks and the payment model are not finalized.
Built-in wallet security
The planned MPC model is intended to keep key material outside agent context and limit agent permissions.
One API across operations
The future API is intended as one interface for receiving, exchanging, and sending supported digital assets.
The planned agent-wallet flow.
A conceptual path through the BroWallet Skill or CLI; real wallets and operations are not yet available.
Connect your agent
A machine-readable process for creating an agent identity and connecting to BroWallet is planned.
Open a wallet
Managed-wallet creation and deposit-address provisioning are planned, not currently available operations.
Add funds
Asset receipt and real-time balance reads are in development.
Swap or send
Swaps, cross-network routes, and payments are planned operations and will depend on providers.
Stay informed
Statuses, receipts, and notifications are planned for the future API.
Planned network-fee abstraction.
We are exploring a model in which agents do not separately maintain native gas tokens. Networks, assets, and payment mechanics are not finalized.
A simpler agent experience
The future flow is intended to reduce the need to maintain a separate native token on every network.
Clear cost before execution
Showing the expected cost before confirming an operation is planned.
One machine-readable result
Future operations are intended to return machine-readable statuses and receipts.
# What your agent getsquote = "One clear quote"# Planned gas abstractionnative_gas_balance = falsereceipt = "Planned operation receipt"# Agent experienceagent_balance = "One-balance concept"# Native gas tokengas_token = "Planned abstraction"Three future flows.
Deposits, swaps, and withdrawals are shown as product concepts and are not yet available for real funds.
Deposit
Deposit-address creation, incoming-fund tracking, and agent balance updates are planned.
Relay swap
Route discovery and asset exchange are planned and will depend on available external providers.
Withdrawal
Asset withdrawal with status tracking is being considered as a future flow.
Possible use cases after BroWallet launches.
Automated commerce, treasury operations, and embedded wallets are future scenarios, not currently available functions.
Let agents pay for tools and services
A future flow could give agents a controlled balance for APIs, services, and machine-to-machine purchases.
Move and rebalance funds automatically
After launch, agents may be able to consolidate balances and route liquidity under business rules.
Add wallets to your own AI experience
Wallet creation and asset operations may later be considered for copilots, marketplaces, bots, and autonomous products.
Autonomous does not mean unrestricted.
Server-side limits are planned for the future product; their final implementation is still being validated.
Scoped capabilities
Credentials are planned to be scoped by wallet, network, asset, operation type, and amount.
Proof and replay protection
Signed hashes, nonces, timestamps, rotation, and revocation are being considered for future authorization.
Payload-bound execution
The recipient, asset, amount, calls, expiry, and fee ceilings are planned to be bound to an approved operation.
Safe retries
Future mutations are planned to use an idempotency key to help avoid duplicate operations.
Dual-ledger reconciliation
Planned reconciliation is intended to compare product records with provider transactions and blockchain data.
Circuit breakers
Limits, allowlists, anomaly detection, and emergency pause are being considered as future risk controls.
Planning an agent that may need to work with funds?
Tell us about the planned workflow and leave your contact details for BroWallet updates and future early access.