Skip to main content
AI agents need wallets to hold funds, sign transactions, and pay for services. Dynamic provides two patterns depending on whether the agent acts autonomously or on behalf of a user.

​
Wallet patterns for agents

​
Server wallets — autonomous agents

Server wallets are wallets your backend creates and controls. No user is required to sign; your code signs directly. When to use this:
  • The agent acts on its own behalf (not a user’s)
  • Fully automated flows: bots, scheduled tasks, pipelines
  • You need to provision many agent wallets programmatically
How it works:
  1. Authenticate with your API token
  2. Create a wallet via the Node SDK — you get back an address and signing credentials (key shares)
  3. Store the key shares securely; use them to sign messages and transactions on any request

Server Wallets Setup

Create wallets, sign transactions, and manage key shares from your backend.

​
Delegated access — agents acting for users

Delegated access lets your agent sign transactions on behalf of a user who has explicitly approved it. The user’s embedded wallet stays user-owned; they grant your server limited signing rights. When to use this:
  • The agent acts on behalf of a specific user
  • You want the user to stay in control and be able to revoke access
  • Multi-user apps where each user has their own wallet the agent uses
How it works:
  1. User authenticates and approves delegation via the Dynamic SDK
  2. Dynamic encrypts the user’s signing credentials and delivers them to your server via webhook
  3. Your server decrypts and stores credentials per user
  4. On each agent action, fetch the user’s credentials and sign

Delegated Access Overview

How delegated access works, security considerations, and dashboard configuration.

​
Agent payments

Agents often need to pay for API access or services without a human in the loop. See Agent Payments for how to wire up HTTP 402 payment flows — including x402 and Tempo MPP — using Dynamic server wallets.