Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.dynamic.xyz/docs/llms.txt

Use this file to discover all available pages before exploring further.

AI agents need wallets to hold funds, sign transactions, and pay for services. Dynamic gives you two patterns — pick the one that matches who the agent acts for.

​
Server wallets — autonomous agents

Wallets your backend creates and controls. No user is required to sign; your code signs directly using MPC key shares. Use this when
  • The agent acts on its own behalf, not a user’s
  • Flows are fully automated: bots, scheduled tasks, pipelines
  • You need to provision many agent wallets programmatically
SDK support
Node Python Rust Go · Soon Java · Soon Ruby · Soon

Set up Server Wallets

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

​
Delegated access — agents acting for users

Your agent signs 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 and can revoke at any time. Use this when
  • The agent acts on behalf of a specific user
  • You want the user to stay in control of their wallet
  • Multi-user apps where each user has their own wallet the agent uses
SDK support Delegated access has two legs — a client SDK to trigger the user’s consent prompt, and a server SDK to use the delegated materials afterward.
Trigger
React JavaScript React Native Swift Kotlin Flutter Unity
Use
Node Python Rust Go · Soon Java · Soon Ruby · Soon

Set up Delegated Access

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. Dynamic server wallets plug into HTTP 402 payment flows — including x402 and Tempo MPP — so the agent can sign, pay, and retry automatically.

Agent Payments

Wire HTTP 402 payment flows to a Dynamic server wallet.