Agent wallets for AI agents
Programmable session keys, policy-based spending limits, x402, and sub-100ms wallet creation. The embedded wallet for AI agents.
No credit card required • Free testnet accounts
50+ teams use Openfort.10M+ transactions sent by 50+ teams.
Read their storiesSEE WHY TEAMS love Openfort→
Give the agent a key. Keep the rules.
Issue a session key scoped by contract address, function selector, spend cap, and expiry. The agent signs transactions inside the policy. Revoke instantly. No shared secrets, no off-chain trust.
HTTP-native payments for agents
Openfort agent wallets natively support x402 for HTTP-native payments, plus subscriptions, batch operations, and one-click purchases. Drop the agent in front of paid APIs and let it pay per call inside its policy.
Open-source key management via OpenSigner
Agent keys are generated by OpenSigner (opensigner.dev), our open-source self-hostable signing service that uses TEEs and MPC. Run it inside your own infrastructure so no third party can sign on the agent’s behalf.
Build the rest of the stack with Openfort
Agent wallets plug into the same SDK as embedded wallets, smart accounts, and wallet automations.
Embedded wallets
Non-custodial embedded wallets powered by OpenSigner, with full key export and self-hosting options. Read more
ERC-4337 smart accounts
Native ERC-4337 + EIP-7702 smart accounts with paymasters, session keys, and batched operations. Read more
Wallet automations
TEE backend wallets for server-side key storage with permissions and automatic transaction execution. Read more
Frequently Asked Questions
Can't find your answer?
An agent wallet is a non-custodial wallet purpose-built for AI agents. It uses programmable session keys, policy-based spending limits, and HTTP-native payment standards like x402 so an agent can transact autonomously inside the rules you define — how much it can spend, which contracts it can call, when its access expires.
Create a non-custodial wallet for the agent with the Openfort SDK, attach a session key scoped by contract address, spend cap, and expiry, and let the agent sign transactions inside that policy. Full guide and code at openfort.io/docs/overview/building-with-cli.
Openfort provides embedded wallets purpose-built for AI agents: programmable session keys, policy-based spending limits, x402 support, and sub-100ms wallet creation. Agents get their own non-custodial wallet, and you control what they can sign, how much they can spend, and which contracts they can call.
Yes. Openfort agent wallets natively support x402 for HTTP-native agent payments alongside session keys, subscriptions, batch operations, and one-click purchases.
Keys are generated by OpenSigner, our open-source key management system, using TEEs and MPC. You can self-host OpenSigner so the operator never has unilateral access to the agent’s key. Session keys add a second layer: even if a key is leaked, the policy enforces spending caps and contract allowlists.
Yes. Openfort supports multiple wallets per user across EVM and Solana chains. You can give each agent its own wallet with its own policy, or share one wallet across agents with per-agent session keys.