privy-agent-wallets) lets consumers authenticate, fund, and transact from assistants like Claude Code, Cursor, Cline, and Windsurf without writing any integration code.
Go to agents.privy.io to track agent activity and spend in the agent sandbox.
Design principles
- CLI-first distribution: Agents already execute shell commands. A CLI is the most natural interface for agent-driven wallets.
- Skill-based discovery: The skill file teaches agents how to authenticate and transact without human guidance beyond the initial login.
- Browser-based funding: The human owner retains a visual dashboard to check balances, view transaction history, and onramp funds, keeping the human in control.
- Cryptographic authorization: Each CLI session generates a P-256 keypair which is used to sign RPC requests. The agent is never given the wallet private key.
How it works
- The CLI generates a local P-256 keypair and opens a browser for authentication.
- The human logs in through Privy and grants the agent signer access to their wallets.
- The CLI stores the session in the OS credential manager (or an encrypted local file as fallback).
- For every transaction, the CLI signs an authorization payload and sends it to the agent server, which verifies the signature, injects app credentials, and forwards the request to Privy’s API.
Getting started
- For humans
- For agents
Visit the agent sandbox
Go to agents.privy.io to create an account, view wallets, and manage agent activity.
Log in
Start the authentication flow. This generates a keypair, opens a browser window, and waits for credentials.In the browser, complete the Privy login and approve signer access. The browser displays a JSON credential blob. Copy it and paste it back into the terminal to complete login.
Fund wallets
Open the agent sandbox in a browser to add funds via onramp:The agent sandbox at agents.privy.io provides a visual interface to view balances, review transaction history, and onramp funds into the wallet.
Supported RPC methods
Ethereum
| Method | Description |
|---|---|
personal_sign | Sign a plaintext message |
eth_sendTransaction | Send a transaction |
eth_signTransaction | Sign without broadcasting |
eth_signTypedData_v4 | Sign EIP-712 typed data |
secp256k1_sign | Raw secp256k1 signature |
eth_sign7702Authorization | EIP-7702 authorization |
eth_signUserOperation | Sign a user operation (ERC-4337) |
Solana
| Method | Description |
|---|---|
signTransaction | Sign a Solana transaction |
signAndSendTransaction | Sign and broadcast a transaction |
signMessage | Sign an arbitrary message |
Session and credential storage
The CLI attempts to use the OS-backed credential manager when available, and otherwise falls back to storing session data in an encrypted file at~/.privy/session.json. It is the responsibility of the agent or user to install any required prerequisites for the OS credential manager.
| Platform | Credential manager | Prerequisites |
|---|---|---|
| macOS | Keychain (security CLI) | None — available by default |
| Linux | libsecret (secret-tool CLI) | sudo apt install -y libsecret-tools (Debian/Ubuntu) |
| Windows | PowerShell SecretManagement | Install-Module Microsoft.PowerShell.SecretManagement |
~/.privy/session.json. This file is not portable between machines.
Each session contains:
- The app ID for the Privy agent wallet app
- Ethereum and Solana wallet IDs and addresses
- The P-256 private key used to sign RPC requests
- A creation timestamp
Learn more
Agent CLI
Track agent activity, view balances, and manage wallets.
Agentic wallets
Build developer-controlled agent wallets with policy guardrails.
x402 payments
Enable HTTP-native payments for APIs and digital content.
MPP integration
Machine-to-machine payments over HTTP with Privy wallets.
Gas sponsorship
Sponsor gas fees for agent transactions.