Problem
Giving an AI agent an API key today grants everything the key can do. The safe pattern is an on-chain allowance: funds an agent can spend up to a cap, reclaimable by the owner.
Proposal
Build on the existing time-locked escrow to expose an allowance primitive: createAllowance(agent, cap, expiry) — the agent can draw down up to cap until expiry; the owner can revoke anytime; unspent funds return automatically.
Pairs with the spend-mandate RFC in furlpay-x402: mandates bound what the facilitator settles, allowances bound what the wallet can sign at all — defense in depth.
Problem
Giving an AI agent an API key today grants everything the key can do. The safe pattern is an on-chain allowance: funds an agent can spend up to a cap, reclaimable by the owner.
Proposal
Build on the existing time-locked escrow to expose an allowance primitive:
createAllowance(agent, cap, expiry)— the agent can draw down up tocapuntilexpiry; the owner can revoke anytime; unspent funds return automatically.Pairs with the spend-mandate RFC in furlpay-x402: mandates bound what the facilitator settles, allowances bound what the wallet can sign at all — defense in depth.