Payment Delegation Key (PDK)
PDK is optional. For fully permissionless access, you can use AiMo Network directly with a signer parameter (supports both Base and Solana). See the SDK Reference to learn more.
A Payment Delegation Key (PDK) lets AI agents pay for services on your behalf—without giving them full control of your wallet.
Overview
Traditional AI platforms require you to create an account, top up credits, and generate an API key. Your funds sit in their custody, locked to that single platform. PDKs work differently: you delegate specific permissions to an agent while your funds stay in your own wallet until the moment of use.
When you create a PDK, you define exactly what the agent can do—spending limits, expiration, allowed recipients. The agent operates autonomously within those boundaries, and you retain full custody of your funds.
Permission Parameters
When generating a PDK, users configure permissions to control what the AI agent can do. These are the core parameters:
| Parameter | Type | Description |
|---|---|---|
max_transaction_value | number | Maximum value allowed per single transaction |
daily_spending_limit | number | Total amount that can be spent within 24 hours |
valid_until | timestamp | When the PDK expires and becomes invalid |
allowed_recipients | address[] | Addresses the PDK can send transactions to |
For most use cases, setting a daily_spending_limit and valid_until provides sufficient protection while allowing agents to operate autonomously.
PDK is built on top of Privy's policy engine. For advanced configurations like contract allowlists, calldata restrictions, and typed data signing rules, see the Privy documentation.