Last updated: July 18, 2026.
An agent wallet has two jobs: sign autonomously inside tight guardrails, and route payments on the rails the agent transacts against. Nine platforms cover that market in 2026, splitting roughly into full-stack bundles (wallet plus payments plus compliance) and signing primitives (wallet only, bring your own payment layer). The ranking below is for developers picking a stack.
For the architectural walkthrough and the custody model, see the AI agents solution page and agent wallet identity, permissions, and compliance. This post is the agent-wallet spoke of a larger set — the Wallet-as-a-Service pillar, plus embedded wallets, Ethereum developer wallets, and stablecoin-payment wallets.
What is an agentic wallet?
An agentic wallet — also called an AI agent wallet — is the core of any agent wallet infrastructure stack: a wallet an autonomous AI agent controls to hold funds and transact on its own, inside limits a developer sets. Unlike a normal embedded wallet (operated by a human clicking "confirm"), an agent wallet is designed to sign without a human in the loop while staying bounded by policy: which contracts it can call, how much it can spend, and over what time window.
Two design choices define an agentic wallet:
- Where the policy lives — enforced on-chain (encoded in a smart account / session key, independently verifiable) or off-chain (checked by the provider's API before signing).
- Which rails it pays on — stablecoin/crypto only, or dual-rail with card networks (Visa/Mastercard) — and whether it speaks agent-payment protocols like x402, AP2, or MCP.
The best agentic wallet for your build depends on those two axes plus your framework stack and whether you need to self-host. The rest of this post compares the platforms on exactly that.
The 9 Agent Wallet Platforms at a Glance
| Rank | Provider | Tier | Payment Rails | Spending Controls | Self-hostable | Free Tier |
|---|---|---|---|---|---|---|
| 1 | Openfort | Signing primitive | Stablecoin / crypto (BYO) | On-chain session keys | Yes (OpenSigner) | 2,000 ops/mo |
| 2 | Crossmint | Full-stack | Stablecoin + Card (Visa/MC) | Dual-key + limits | No | 1,000 MAW |
| 3 | Turnkey | Signing primitive | Stablecoin / crypto (BYO) | TEE policy engine | No | 25 signatures/mo |
| 4 | Coinbase AgentKit | Full-stack | Stablecoin (Base only) | None built-in | Yes (SDK) | Free |
| 5 | Privy | Signing primitive | Stablecoin / crypto (BYO) | Off-chain policy API | No | 499 MAUs |
| 6 | Dynamic | Signing primitive | Stablecoin / crypto (BYO) | Basic | No | Free tier |
| 7 | Alchemy x402 | Signing primitive | USDC (Base) | Auto top-up only | No | Not specified |
| 8 | Phantom MCP | Signing primitive | Stablecoin / crypto | None specified | No | Free |
| 9 | Thirdweb Engine | Full-stack | Stablecoin / crypto (BYO) | Scoped session keys | Yes (self-hosted) | Free (self-hosted) |
1. Openfort
Openfort (that's us 👋) is open-source wallet infrastructure with native smart accounts. Its backend wallet product is the agent wallet layer: ERC-4337 and EIP-7702 smart accounts with on-chain session keys that encode what the agent key can do — which contracts, which methods, what spend cap, what time window. Policy enforcement is on-chain, which makes it transparent, composable, and independently verifiable.
Unlike every other agent wallet on this list, Openfort's signer (OpenSigner) is open-source and self-hostable. For teams with regulatory or sovereignty requirements, that is the only path to audit the full signing infrastructure and remove vendor lock-in. For teams building agents that interact with other on-chain contracts, on-chain policy enforcement composes naturally — any contract can verify the agent's permissions without trusting an API.
Key Features
- Native ERC-4337 and EIP-7702 smart accounts with session keys
- On-chain policy enforcement (transparent, composable, auditable)
- Open-source signer with self-hosting path via OpenSigner
- Gas sponsorship included from the free tier
- Backend wallets in TEE, or self-hosted, for autonomous signing
- Any OIDC authentication provider + custom JWT
- Multi-chain EVM support with Solana on the wallet and signing layer
Pricing
Included in the Openfort platform. Free tier covers 2,000 operations per month across wallet creation, signing, and gas sponsorship. Paid plans are usage-based — one operation is a wallet creation or a transaction, no per-signature premium.
Openfort Agent Wallet Snapshot
| Feature | Openfort |
|---|---|
| Tier | Signing primitive |
| Policy enforcement | On-chain session keys + basic off-chain API |
| Chain support | Multi-chain EVM (+ Solana wallet/signing) |
| Self-hosting | Yes (OpenSigner) |
| AI framework support | API-first (works with any framework) |
| Best for | On-chain verifiable agent permissions, self-hosting, multi-chain agent products |
Why developers choose Openfort
Openfort is the only agent wallet with on-chain enforceable policies, an open-source signer, and a self-hosting path. For teams that want architectural control — because of compliance, because of composability, or because they plan to run agents at scale and do not want signer pricing baked into every transaction — Openfort is the default starting point. The payments layer is BYO: if the agent needs onramps or card rails, pair Openfort with a payment provider.
2. Crossmint
Crossmint is the full-stack agent wallet platform. It ships wallets, stablecoin orchestration across 50+ chains, onramps and offramps, KYC/AML/Travel Rule compliance, and — uniquely — card network integration via Lobster Cash. Lobster Cash is an open payment standard built with Visa, Solana, Circle, and Stytch that gives agents virtual credit cards with spending limits alongside USDC wallets with human approval flows. Raw card data and private keys are never exposed to the agent's context.
Crossmint is MiCA CASP licensed across all 27 EU member states and is working toward a PSD2 Payment Institution license in Spain. For regulated products, the compliance surface is the biggest differentiator.
Key Features
- Dual-key non-custodial architecture (owner key + TEE-sealed agent key)
- Stablecoin rails + Visa/Mastercard agentic payment protocols via Lobster Cash
- Smart contract wallets by default (EVM, Solana, Stellar)
- Native onramps (card, Apple Pay, Google Pay in 160+ countries)
- Native offramps (100+ countries, mobile money, cash agents)
- Built-in KYC/AML/Travel Rule compliance
- MiCA CASP licensed in the EU
- Spending limits, human approval flows, policy-based guardrails
Pricing
1,000 monthly active wallets free — includes wallets, payments, and compliance. Paid tiers are usage-based.
Openfort vs. Crossmint
| Feature | Openfort | Crossmint |
|---|---|---|
| Open-source | Yes (MIT) | No |
| Self-hostable signer | Yes (OpenSigner) | No |
| Card network rails | No | Yes (Visa, Mastercard) |
| Native onramps/offramps | No | Yes |
| MiCA CASP license | No | Yes |
| Policy enforcement | On-chain session keys | Dual-key + spending limits |
Why developers choose Crossmint
Crossmint is the pick when the agent has to transact with merchants that do not accept crypto, or when EU compliance is a product requirement. No other platform bundles card networks, onramps, offramps, and a MiCA license with an agent wallet. The trade-off is ecosystem depth: Crossmint runs on proprietary infrastructure, so you cannot self-host the signer or audit the full path end to end.
3. Turnkey
Turnkey provides the strongest key-level security model in the agent wallet market. Keys are generated and signed inside AWS Nitro Enclaves, never reconstructed externally. Full remote attestation proves the exact code and config running in the enclave — independently verifiable by third parties. Signing latency is 100–150ms, and Turnkey operates at the cryptographic curve layer (Ed25519, Secp256k1) so chain coverage is wide by default.
Turnkey's agent wallet offering is Enterprise-only, with per-signature pricing as low as $0.0015 at scale. It is the platform for high-frequency autonomous systems, trading desks, and multi-tenant signing architectures.
Key Features
- TEE-based key management (AWS Nitro Enclaves), keys never reconstructed
- Full remote attestation and reproducible builds
- Org-level policy engine enforced inside the TEE at signing time
- Curve-layer signing (Ed25519 + Secp256k1) — 50+ chains
- 100–150ms signing latency
- Key import/export, key quorum, multi-party approvals
- Full auth suite: passkeys, email, SMS (custom), OAuth, Telegram, custom flows
Pricing
Free tier: 25 signatures per month, up to 100 wallets. Pro: $99/month, $0.05/signature, up to 2,000 wallets. Enterprise (required for agent use cases): custom, as low as $0.0015/signature.
Openfort vs. Turnkey
| Feature | Openfort | Turnkey |
|---|---|---|
| Open-source | Yes (MIT) | No |
| Self-hostable signer | Yes (OpenSigner) | No |
| Policy enforcement | On-chain session keys | Inside TEE (curve layer) |
| Custom JWT/OIDC | Yes | No |
| Gas sponsorship | Free tier | Enterprise/custom only |
| Per-signature floor | Operation-based (no per-sig fee) | $0.0015 at enterprise scale |
Why developers choose Turnkey
Turnkey is the pick when the signing layer has to be cryptographically verifiable — independently — and when signing frequency pushes per-transaction costs to the center of the pricing conversation. Trading desks, market makers, custodians, and high-volume autonomous systems build on Turnkey for the TEE plus attestation model. BYO stack means onramps, offramps, card rails, and consumer UX are all your responsibility.
4. Coinbase AgentKit
Coinbase AgentKit is Coinbase's open-source SDK for agent wallets on Base. It provisions CDP smart wallets, supports the OpenAI Agents SDK, and ships with no built-in spending limits — you add them through the application layer. AgentKit is free, open-source, and the fastest path to an agent wallet on Base.
Key Features
- Open-source SDK
- Coinbase Developer Platform smart wallets on Base
- OpenAI Agents SDK integration
- Free to use (blockchain gas fees apply)
- Composable with CDP onramp/offramp (Coinbase Pay)
Pricing
Free SDK. Blockchain gas fees apply. Coinbase's managed services (onramp, staking) have their own pricing.
Openfort vs. Coinbase AgentKit
| Feature | Openfort | Coinbase AgentKit |
|---|---|---|
| Open-source | Yes | Yes |
| Chain support | Multi-chain EVM (+ Solana) | Base |
| Built-in spending controls | On-chain session keys | None |
| Card network rails | No | No |
| AI framework coverage | API-first | OpenAI Agents SDK |
| Onramp/offramp | No | Yes (Coinbase Pay) |
Why developers choose Coinbase AgentKit
AgentKit is the pick for Base-native agents that want free, open-source wallet infrastructure with onramp and offramp in the same ecosystem. It is narrow — Base only, no built-in spending controls, no multi-framework support — but if that is the fit, it is the shortest path.
5. Privy
Privy (acquired by Stripe in June 2025) provides Server Wallets as its agent wallet offering. Keys live in a TEE combined with Shamir Secret Sharing; policies are off-chain and scoped per wallet (transfer limits, approved protocols, recipient restrictions, operating time windows). Privy's coupling with Stripe and the Bridge stablecoin rails makes it a natural fit for agents in the Stripe ecosystem.
Key Features
- Server wallets with TEE + SSS key management
- Off-chain policy enforcement with transfer limits, allowlists, time windows
- EVM, Solana, Bitcoin support
- Agentic CLI for AI-driven wallet operations
- Stripe/Bridge integration for indirect fiat payment paths
Pricing
Included in Privy platform pricing. Free tier up to 499 MAUs; Core $299/month for up to 2,500 MAUs; usage-based above 10K MAUs, 50K signatures, or $1M monthly transaction volume.
Openfort vs. Privy
| Feature | Openfort | Privy |
|---|---|---|
| Open-source | Yes | No |
| Policy enforcement | On-chain session keys | Off-chain API, per-wallet scoped |
| Autonomous (sessionless) agents | Yes (native) | Requires user sessions |
| Self-hostable signer | Yes | No |
| Native smart accounts | Yes (ERC-4337, 7702) | Via third-party integration |
| Free tier | 2,000 ops/mo | 499 MAUs |
Why developers choose Privy
Privy is the fast path for consumer agent products in the Stripe ecosystem. The agentic CLI, user-sessioned server wallets, and Stripe billing integration shorten the ramp. Limitations: per-wallet policy scoping means a missed API call leaves a wallet uncovered, and the user-session requirement doesn't natively fit fully autonomous, sessionless agents.
6. Dynamic
Dynamic (acquired by Fireblocks in 2025) covers embedded wallets for hybrid human-plus-agent products. The architecture is configurable (MPC or smart contract wallet) and spans EVM, Solana, and Cosmos. Dynamic's strongest card is onboarding UX — a polished auth modal that fits products where users and agents share the same wallet surface.
Key Features
- Embedded wallets: MPC or smart contract architecture
- EVM, Solana, Cosmos chain support
- Polished auth UI with extensive customization
- Multi-wallet aggregation for users bringing external wallets
- Session management and JWT-based auth
Pricing
Included in platform pricing. Free tier available; usage-based pricing for growth and enterprise tiers.
Openfort vs. Dynamic
| Feature | Openfort | Dynamic |
|---|---|---|
| Native smart accounts | Yes (ERC-4337, 7702) | Configurable (MPC or SC) |
| Agent-specific spending controls | On-chain session keys | Basic |
| Open-source | Yes | No |
| Chain support | Multi-chain EVM (+ Solana) | EVM, Solana, Cosmos |
| Strategic direction | Independent | Part of Fireblocks |
Why developers choose Dynamic
Dynamic is the pick when the product serves both humans and agents and the onboarding UX has to be shared across both. Agent-specific capabilities are less developed than dedicated agent platforms — Dynamic's strength is the UX layer, not the policy engine. Post-Fireblocks, strategic direction for agent use cases is unclear.
7. Alchemy Agent Wallet (x402)
Alchemy's Agent Wallet is purpose-built for the x402 pay-per-call API protocol on Base. When an agent's compute credits run out, the wallet auto-tops up with USDC. The fit is narrow but clean: API metering and micropayment-for-compute use cases on Base.
Key Features
- TEE-based signing
- x402 protocol integration
- Automated USDC top-up on Base when compute credits run out
- Base-native USDC support
Pricing
Not specified.
Openfort vs. Alchemy x402
| Feature | Openfort | Alchemy x402 |
|---|---|---|
| Use case | General-purpose agent wallets | Pay-per-call API metering |
| Chain support | Multi-chain EVM (+ Solana) | Base (USDC) |
| Spending controls | On-chain session keys | Auto top-up only |
| Open-source | Yes | No |
| Framework support | API-first | Not specified |
Why developers choose Alchemy x402
Alchemy x402 is the pick when the agent's transaction surface is literally pay-per-call APIs on Base. For any broader agent use case, it does not cover enough of the wallet layer on its own.
8. Phantom MCP Server
Phantom's MCP Server lets MCP-compatible AI clients connect to a user's Phantom wallet on Solana. Agents can sign transactions, execute swaps, and transfer tokens within whatever limits the user configures on their Phantom wallet. Free, low-friction, and the fastest way to let an agent transact from a user's existing Solana wallet — but Phantom is a consumer wallet, not a purpose-built agent platform.
Key Features
- MCP server integration with consumer Phantom wallet
- Sign transactions, execute swaps, transfer tokens
- Solana-native (plus Phantom-supported chains)
- Free (consumer wallet)
Pricing
Free.
Openfort vs. Phantom MCP
| Feature | Openfort | Phantom MCP |
|---|---|---|
| Purpose | Purpose-built agent infrastructure | Consumer wallet + MCP layer |
| Programmatic wallet provisioning | Yes | No (users bring their Phantom wallet) |
| Spending controls | On-chain session keys | None specified |
| Fleet management | Yes | No |
| Chain support | Multi-chain EVM (+ Solana) | Phantom-supported chains |
Why developers choose Phantom MCP
Phantom MCP is the pick when the agent needs to operate a user's existing Solana wallet, not a platform-provisioned agent wallet. Useful for consumer-facing agents that act on behalf of Phantom users. Not a replacement for a purpose-built agent wallet platform.
9. Thirdweb Engine
Thirdweb Engine is the backend wallet and transaction layer of the broader Thirdweb platform, and it doubles as an agent wallet with the widest AI-framework coverage on this list. Engine manages server-side wallets, scoped session keys, and a transaction queue with automatic gas handling across 700+ EVM chains. It is open-source and free when self-hosted.
Key Features
- Backend/server wallets with scoped session keys for agents
- Transaction queue with nonce management and gas handling
- Broad AI-framework coverage: OpenAI Agents SDK, LangChain, CrewAI, AutoGen, LlamaIndex, and MCP
- 700+ EVM chains
- Open-source; self-hostable or managed cloud
- Composable with third-party paymasters and bundlers
Pricing
Free when self-hosted (blockchain gas fees apply). Managed Engine plans and premium features are usage-based.
Openfort vs. Thirdweb Engine
| Feature | Openfort | Thirdweb Engine |
|---|---|---|
| Open-source | Yes | Partial |
| Self-hostable signer | Yes (OpenSigner) | Yes (Engine) |
| Policy enforcement | On-chain session keys | Scoped session keys |
| Chain support | Multi-chain EVM (+ Solana) | 700+ EVM |
| AI framework coverage | API-first | 6+ frameworks |
| Native smart accounts | Yes (4337 + 7702) | Yes (4337) |
Why developers choose Thirdweb Engine
Engine is the pick when the agent has to plug into many AI frameworks and you want a self-hostable transaction backend across a wide EVM footprint. The trade-off is that agent wallets are one feature inside a large platform, so policy depth and agent-specific tooling are less focused than a dedicated primitive. Solana and card rails are out of scope.
Detailed Feature Comparison
| Feature | Openfort | Crossmint | Turnkey | Thirdweb | Coinbase AgentKit | Privy | Dynamic | Alchemy x402 | Phantom MCP |
|---|---|---|---|---|---|---|---|---|---|
| Tier | Primitive | Full-stack | Primitive | Full-stack | Full-stack | Primitive | Primitive | Primitive | Primitive |
| Stablecoin rails | Yes | Yes | Yes | Yes | Yes (Base) | Yes | Yes | Yes (USDC) | Yes |
| Card network rails | No | Yes | No | No | No | No | No | No | No |
| Open-source | Yes | No | No | Partial | Yes | No | No | No | No |
| Self-hostable | Yes (OpenSigner) | No | No | Yes (Engine) | Yes (SDK) | No | No | No | No |
| On-chain policy | Yes (session keys) | Partial | Enclave | Session keys | No | No | No | No | No |
| Native smart accounts | Yes (4337 + 7702) | Yes (SC) | 7702 on custom | Yes | Yes (CDP SC) | Via integration | Configurable | No | No |
| Framework coverage | API-first | API-first | API-first | 6+ frameworks | OpenAI SDK | Agentic CLI | API-first | Not specified | MCP |
| Agent-payment protocols | MCP server; x402 | Card + x402 | — | MCP | x402 | — | — | x402 | MCP |
| EU/MiCA compliance | No | Yes | No | No | No | No | No | No | No |
| Free tier | 2,000 ops/mo | 1,000 MAW | 25 sigs/mo | Free (self-hosted) | Free | 499 MAUs | Yes | Not specified | Free |
Other agentic wallets and agent-payment tools to consider
The nine above are the platforms most developers shortlist, but the category is moving fast and a few more names show up in 2026 agent-wallet roundups. They cover adjacent slices — smart-account standards, agent-payment networks, and decentralized key management:
| Tool | Angle |
|---|---|
| Safe | Smart-account and multisig standard; agents run on Safe accounts with modules and guards for policy |
| Cobo | MPC custody and wallet-as-a-service with policy controls, for agent treasuries |
| Circle | Programmable wallets, USDC, and Gas Station; agent-oriented wallet tooling |
| Skyfire | Payment and identity network purpose-built for agent-to-agent and agent-to-service payments |
| Nevermined | Metering and payments rails for agent-to-agent services |
| Lit Protocol | Decentralized key management (MPC/TSS) with programmable signing for agents |
| Composio / GOAT | Agent tool/action frameworks that add on-chain wallet actions to agents |
| Coca, FluxA | Newer smart-account wallet entrants aimed at consumer and agent use |
These are worth tracking, but for a production agent stack the nine ranked platforms remain the primary options.
Where to Start
If you are building an agent product from scratch and do not yet know which constraints matter most, Openfort is a defensible default: open-source, self-hostable, native smart accounts with on-chain session keys, and a free tier that covers 2,000 operations per month including gas sponsorship. If the agent needs card network rails or EU compliance out of the box, start with Crossmint instead. If signing frequency and attestation drive the pick, start with Turnkey.
For the longer-form walkthrough of the architecture decisions behind each platform, see the AI agents solution page.
Related guides
- Best Wallet-as-a-Service (WaaS) providers — the wallet-infrastructure pillar
- Best embedded wallets in 2026 — user-facing embedded wallet SDKs
- Best Ethereum wallets for developers — the EVM developer-wallet view
- Best embedded wallet providers for stablecoin payments — wallets tuned for USDC/USDT payments