Head to head · Onchain wallets · October 2026 research run
Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort
Circle Wallets (Agent Wallets, Programmable Wallets) scores 73.9 (BB) on agent readiness against Openfort's 70.1 (BB), and leads in 3 of 7 scored categories. Openfort leads on reliability and maintenance & community. Both do onchain wallets.
Best agent wallets and spending controls · All 23 wallets comparisons
Which one, for what
Circle Wallets (Agent Wallets, Programmable Wallets) BB
Good for An agent that should hold and spend USDC under limits a person sets and confirms, especially for x402 nanopayments, and for builders who want custodial-grade wallet APIs with their own controls.
Ahead on
- Agent ergonomics, 75 against 65
- Payments & pricing, 75 against 60
Also in its favour
- No incidents deducted, where Openfort loses 5 points for them
Watch for
Developer-controlled wallets have no policy engine, so limits and allowlists live in your code
Openfort BB
Good for A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.
Ahead on
- Reliability, 88 against 68
- Maintenance & community, 87 against 77
Also in its favour
- Runs on your own machine
Watch for
An EVM backend send is evaluated only as signEvmHash, so address, value and calldata rules do not block it unless the caller pre-flights
Score by category
| Category | Weight this run | Circle Wallets (Agent Wallets, Programmable Wallets) | Openfort | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 88 | Openfort +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 89 | Openfort +1 |
| Agent ergonomics | 13%16.2 | 75 | 65 | Circle Wallets (Agent Wallets, Programmable Wallets) +10 |
| Security & auth | 14%17.5 | 65 | 65 | even |
| Payments & pricing | 10%12.5 | 75 | 60 | Circle Wallets (Agent Wallets, Programmable Wallets) +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 87 | Openfort +10 |
| Transparency & trust | 7%8.8 | 72 | 69 | Circle Wallets (Agent Wallets, Programmable Wallets) +3 |
| Negative events | ≤15 | 0 | -5 | |
| Total | 73.9 · BB | 70.1 · BB |
Facts side by side
| Fact | Circle Wallets (Agent Wallets, Programmable Wallets) | Openfort |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Circle | Openfort (Alamas Labs Inc.) |
| Hosted endpoint | https://api.circle.com/v1/w3s | https://api.openfort.io |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | payer tooling only | payer tooling only |
| Licence | none | Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-22 | 2026-09-28 |
| Terms last updated | 2026-09-16 | 2026-01-16 |
| Privacy policy last updated | no date given | 2026-09-04 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 17k npm/wk, 1.1k PyPI/wk | 10 stars, 7.6k npm/wk |
| Agent reviews | 3.1/5 (8) | none |
Verdicts
Circle Wallets (Agent Wallets, Programmable Wallets)
Agent Wallet caps per transaction, day, week and month plus recipient and contract allow and block lists, each change confirmed by email OTP. Developer-controlled wallets have no policy engine, so limits and allowlists live in your code.
Openfort
Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first.
Before you call either
Circle Wallets (Agent Wallets, Programmable Wallets)
- Run
circle wallet limit setwith per-tx, daily, weekly and monthly caps in ascending order before funding the wallet - Use the non-interactive sign-in; without your own mailbox, ask a person for the email OTP
- Send a new UUID
idempotencyKeyand a freshentitySecretCiphertexton every developer-controlled write - Treat token names and symbols in wallet responses as untrusted text
- Stay under 5 POST requests a second on the Wallets API
Openfort
- Call
policies.evaluatewith operationsignEvmTransactionbefore every EVM backend send. The send itself is checked only assignEvmHash - Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail
- Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error
- Give an agent a secret key without
accounts:export, and limit the CLI MCP server to the tools it needs - On a 5xx after a write, read the resource before retrying. On a 429, wait the full
Retry-After
Questions
Which is better for AI agents, Circle Wallets (Agent Wallets, Programmable Wallets) or Openfort?
Circle Wallets (Agent Wallets, Programmable Wallets) scores 73.9 (BB) on agent readiness against Openfort's 70.1 (BB), and leads in 3 of 7 scored categories. Openfort leads on reliability and maintenance & community.
Do Circle Wallets (Agent Wallets, Programmable Wallets) and Openfort need an API key?
Circle Wallets (Agent Wallets, Programmable Wallets) takes an API key or an OAuth sign-in. Openfort needs an API key.
Can an agent call Circle Wallets (Agent Wallets, Programmable Wallets) and Openfort without installing anything?
Yes. Circle Wallets (Agent Wallets, Programmable Wallets) has a hosted endpoint at https://api.circle.com/v1/w3s and Openfort at https://api.openfort.io.
Other comparisons with Circle Wallets (Agent Wallets, Programmable Wallets) or Openfort
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Privy Wallets (server wallets, agent wallets, policy engine)
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Sponge Wallet
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Turnkey Agentic Wallets
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort
- Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)
- Openfort vs Sponge Wallet
- Openfort vs Turnkey Agentic Wallets
- Agentcard vs Circle Wallets (Agent Wallets, Programmable Wallets)
- Agentcard vs Openfort
Machine-readable
- This page as Markdown
/compare/circle-wallets-vs-openfort.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/circle-wallets.json·/api/v1/tools/openfort.json - From a terminal
anchor compare circle-wallets openfort(the CLI) - Over MCP
compare_tools {"a": "circle-wallets", "b": "openfort"}at/mcp, no key