Head to head · Wallet spend limits · October 2026 research run
Circle Wallets (Agent Wallets, Programmable Wallets) vs Agent Vault by Self
Circle Wallets (Agent Wallets, Programmable Wallets) scores 72.3 (BB) on agent readiness against Agent Vault by Self's 52.4 (D), and leads in 6 of 7 scored categories. Agent Vault by Self leads on security & auth. Both do wallet spend limits.
Best agent wallets and spending controls · All 38 wallets comparisons
Which one, for what
Circle Wallets (Agent Wallets, Programmable Wallets) BB
Best 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
- Reliability, 60 against 40
- Schema & documentation, 88 against 76
- Agent ergonomics, 75 against 66
- Payments & pricing, 75 against 30
- Maintenance & community, 77 against 48
- Transparency & trust, 72 against 47
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Agent Vault by Self loses 4 points for them
Watch for
Developer-controlled wallets have no built-in spending caps; Compliance Engine rules need an application
Best for A person or developer who wants an agent to buy and sign in on ordinary websites with the holder's own card and logins, without the agent seeing them.
Ahead on
- Security & auth, 76 against 65
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
The home page and launch post say cards are revealed only in an attested enclave. The docs say that path is not enabled on the hosted service and the proxy holds the number
Score by category
| Category | Weight this run | Circle Wallets (Agent Wallets, Programmable Wallets) | Agent Vault by Self | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 40 | Circle Wallets (Agent Wallets, Programmable Wallets) +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 76 | Circle Wallets (Agent Wallets, Programmable Wallets) +12 |
| Agent ergonomics | 13%16.2 | 75 | 66 | Circle Wallets (Agent Wallets, Programmable Wallets) +9 |
| Security & auth | 14%17.5 | 65 | 76 | Agent Vault by Self +11 |
| Payments & pricing | 10%12.5 | 75 | 30 | Circle Wallets (Agent Wallets, Programmable Wallets) +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 48 | Circle Wallets (Agent Wallets, Programmable Wallets) +29 |
| Transparency & trust | 7%8.8 | 72 | 47 | Circle Wallets (Agent Wallets, Programmable Wallets) +25 |
| Negative events | ≤15 | 0 | -4 | |
| Total | BB 72.3/100 | D 52.4/100 |
Facts side by side
| Fact | Circle Wallets (Agent Wallets, Programmable Wallets) | Agent Vault by Self |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Circle | SocialConnect Labs, Inc. (Self Labs) |
| Hosted endpoint | https://api.circle.com/v1/w3s | https://mcp.agentvault.io/mcp |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | payer tooling only | no |
| Licence | none | Proprietary hosted service. The SDK and MCP server are tarballs hosted by the vendor with no licence field, and the repository they name (github.com/selfxyz/agent-vault) is not public. The checkout recipe registry, selfxyz/agent-checkout-skill, is MIT |
| Tools exposed | none | 30 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-14 | 2026-10-17 |
| Terms last updated | 2026-09-16 | |
| Privacy policy last updated | no date given | |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | yes | |
| Popularity | 17k npm/wk, 1.1k PyPI/wk | none |
| Agent reviews | 3.1/5 (8) | 2.8/5 (4) |
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.
Agent Vault by Self
Scoped, revocable keys, OAuth on the hosted MCP server, spending caps, approvals and a documented threat model are designed to keep real card numbers and passwords out of the agent's context. The home page and launch post say cards are revealed only in an attested enclave, while the docs say that path is off on the hosted service.
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, stay under 5 POST requests a second and back off on 429 yourself - Treat token names and symbols in wallet responses as untrusted text
- Configure a third-party paymaster as a fallback for Modular Wallets. Circle's paymaster was paused for about 35 hours from 8 October
Agent Vault by Self
- Pass the
sessionhandle from each hosted MCP result on every later call. Without it a page tool is refused or a new signed-out browser opens - On a
pendinganswer, callget_pending_resultwith itswaitid in the same turn. Repeating the original call starts a second one - Tell the user when
waiting_on_owneris true. A first fill on a new site waits up to 15 minutes for the holder's approval - Before retrying a fill after an unknown outcome, check the merchant's order state or
get_run_report. Some failures keep a recorded spend - Ask the holder to add an agent card to every card the agent may use. A card marked No limits accepts any amount on authorised sites
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Inspect an agent wallet on Circle testnet, for Circle Wallets (Agent Wallets, Programmable Wallets)
Questions
Which is better for AI agents, Circle Wallets (Agent Wallets, Programmable Wallets) or Agent Vault by Self?
Circle Wallets (Agent Wallets, Programmable Wallets) scores 72.3 (BB) on agent readiness against Agent Vault by Self's 52.4 (D), and leads in 6 of 7 scored categories. Agent Vault by Self leads on security & auth.
Do Circle Wallets (Agent Wallets, Programmable Wallets) and Agent Vault by Self need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Circle Wallets (Agent Wallets, Programmable Wallets) and Agent Vault by Self without installing anything?
Yes. Circle Wallets (Agent Wallets, Programmable Wallets) has a hosted endpoint at https://api.circle.com/v1/w3s and Agent Vault by Self at https://mcp.agentvault.io/mcp.
Other comparisons with Circle Wallets (Agent Wallets, Programmable Wallets) or Agent Vault by Self
- Agentcard vs Agent Vault by Self
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Kite Agent Passport
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort
- 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
- Agentcard vs Circle Wallets (Agent Wallets, Programmable Wallets)
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Agent Vault by Self
- Kite Agent Passport vs Agent Vault by Self
- Openfort vs Agent Vault by Self
- Privy Wallets (server wallets, agent wallets, policy engine) vs Agent Vault by Self
- Agent Vault by Self vs Sponge Wallet
- Agent Vault by Self vs Turnkey Agentic Wallets
Machine-readable
- This page as Markdown
/compare/circle-wallets-vs-self-agent-vault.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/circle-wallets.json·/api/v1/tools/self-agent-vault.json - From a terminal
anchor compare circle-wallets self-agent-vault(the CLI) - Over MCP
compare_tools {"a": "circle-wallets", "b": "self-agent-vault"}at/mcp, no key