Crypto wallets were designed around a simple assumption: a human signs or does not sign a transaction. That binary model breaks down when an autonomous AI agent needs to execute hundreds of payments per minute, each for a few cents of API access or compute. Wallets are now being retrofitted with session keys, spending caps, and programmable policy engines that grant scoped authority to agents without handing over private keys. The shift is not cosmetic. It changes the custody model, the threat surface, and the infrastructure required to support machine-to-machine commerce at scale.
What Programmable Access Actually Means
A session key is a delegated signing key with embedded constraints. Instead of an agent holding the wallet’s primary private key, the wallet owner authorizes a secondary key that can sign transactions only within specific bounds. Those bounds typically include a maximum spend per transaction, a cumulative cap over a time window, an expiration timestamp, and a restricted set of permitted contract addresses or token types. The key is cryptographically derived and can be revoked by the owner. On networks like Solana, session keys are implemented at the application level through wrapper programs. On EVM chains, account abstraction and smart-contract wallets make this native: the wallet contract itself validates the constraints on-chain before executing any signed operation.
Where Smart-Contract Wallets Fit
Account abstraction, specifically ERC-4337 on Ethereum and its equivalents on Base and other EVM chains, provides the structural foundation for agent-compatible wallets. A smart-contract wallet can encode validation logic directly into its code, meaning that a session key’s spending limits and allowlists are enforced by the contract rather than by an off-chain signer service. When an agent submits a transaction, the wallet contract checks the key, the remaining allowance, the time window, and the target address before executing. If any condition fails, the transaction reverts. This removes the need for a trusted intermediary to broker each payment and aligns with how agent payment standards like x402 and platforms like Coinbase Agent Payments are designed to operate. The agent never possesses the owner’s keys. It possesses a scoped credential that is useless outside its defined parameters.
Spending Limits and Policy Engines
The spending-limit problem is more subtle than it appears. A cap of ten USDC per transaction is meaningless if an agent can submit ten thousand transactions per second. Most implementations combine per-transaction caps with aggregate limits measured over rolling windows, typically hourly or daily. Some wallets add velocity checks that flag abnormal transaction patterns. Policy engines sit above the session-key layer and encode higher-level rules: this agent may pay for inference APIs but not for NFT purchases; this agent may transact only with contracts on a curated allowlist; this agent’s total monthly spend may not exceed five hundred dollars. These policies resemble the authorization rules found in corporate expense management systems, which is not a coincidence. Agent spending is corporate spending, and the controls are converging.
The Threat Surface Has Not Shrunk
A scoped session key reduces blast radius compared to raw key exposure, but it does not eliminate risk. An agent whose session key is compromised can still drain funds up to the cumulative cap before the owner detects and revokes. Revocation latency matters: on Ethereum, revoking a session key requires an on-chain transaction from the owner, which can take minutes under congestion. Some implementations include emergency kill switches that invalidate keys off-chain through a relayer, but this reintroduces a trusted party. A more fundamental problem is policy correctness. A poorly configured allowlist or an overly generous spending window produces the same outcome as no controls at all. The wallet infrastructure is being rebuilt for agents, but the configuration layer where most failures will occur is still manual, poorly tooled, and largely untested at production scale.
Sources
- https://crypto-economy.com/how-ai-agents-are-rewriting-crypto-wallet-rules-through-programmable-access-and-controls/
- https://www.tipranks.com/news/private-companies/interlace-weekly-recap-14
- https://news.bitcoin.com/visa-launches-stablecoin-pilot-with-m-pesa-in-drc-to-test-cross-border-transfers/
- https://en.sedaily.com/finance/2026/07/04/why-samsung-electronics-joined-the-dollar-stablecoin