Wallet infrastructure
PUBLIC PRODUCT REFERENCE
Privy
Agent wallets
Wallet infrastructure for agents to hold funds and transact within guardrails.
At a glance
- Consider for
- Developers embedding wallets into their own agent applications.
- Integration
- SDK, API and CLI
- Payment protocols
- Check integration docs
- Spending controls
- Programmable guardrails; confirm the policy model for your integration.
COMPARE THE DETAILS
Costs, control & compatibility
Provider-reported facts, checked 2026-10-26. “Partial review” identifies an incomplete check; “Not confirmed” does not mean unsupported.
- Networks
- Ethereum, Base, Arbitrum, Polygon, Tempo, and Solana are named on the agent product page. Official source ↗
- Key control
- Developer-owned and user-owned models; scoped agent signers with TEE and key sharding. Official source ↗
- PricingPartial review
- Free developer tier advertises 50K signatures and $1M monthly transaction volume; other usage limits apply. Official source ↗
- Permissions
- Transfer limits, contract allowlists, recipient restrictions, time windows, and approval flows. Official source ↗
- Developer access
- SDK, API, Agent CLI; integrates with MCP servers and custom runtimes. Official source ↗
- Testing
- Dedicated agent sandbox described by provider; no payment test performed here. Official source ↗
Before you integrate
Ownership depends on your integration. Support for MCP-based architectures does not by itself confirm a particular payment protocol or a ready-made MCP server.
Official resources
Before you choose
Use the provider’s documentation to answer these questions for your application.
- Who controls the keys, and how can access be revoked?
- Which spending limits apply to your chosen integration?
- What are the total fees, including funding and network costs?
- Can you try the complete flow in a test environment?