An agent wallet gives an AI a dedicated onchain account with narrowly delegated signing authority. In Darwin Pay, it is a payment source for eligible onchain routes—not a saved card, a general credential vault, or permission to spend without limits.
Privy-backed agent wallets are a planned Darwin Pay integration. They are not available in the production API or MCP tool set yet.
Use Privy as wallet infrastructure
Privy can provision embedded or server wallets and authorize agents through delegated signers. Its policy engine can enforce controls before a transaction is signed, including per-transaction or time-window limits, allowed recipients, allowed contracts, and action-specific rules.
The wallet’s private key or authorization key never enters an AI prompt, tool argument, Action result, or Darwin Vault item. A browser authorization flow may let the user grant a scoped agent permission without giving the agent raw key material.
Bind wallet policy to the payment
Darwin requires the wallet grant and provider policy to cover the exact network, asset, amount, recipient, contract, action, and expiry from the current payment interaction. A broader wallet policy does not broaden the Action. A wallet transaction outside the reviewed interaction remains unauthorized by Darwin.
Privy support is appropriate for onchain settlement, x402, MPP, and other wallet-native routes when the merchant and capability advertise them. It does not make a crypto wallet interchangeable with card checkout, Link, bank debit, or a merchant-specific payment token.
See Privy’s agent wallet overview, delegated signer guide, and agentic app guide for the provider’s current model. 
