Head to head · Wallet onchain · October 2026 research run
Circle Wallets (Agent Wallets, Programmable Wallets) vs Privy Wallets (server wallets, agent wallets, policy engine)
Circle Wallets (Agent Wallets, Programmable Wallets) has a score of 74.1 (BB) against Privy Wallets (server wallets, agent wallets, policy engine)'s 70.1 (BB). Both do wallet onchain. The largest gap is reliability, 20 points.
Circle Wallets (Agent Wallets, Programmable Wallets)Circle · HTTP API
BB74.1/100#50 of 452
Privy Wallets (server wallets, agent wallets, policy engine)Privy (Stripe) · HTTP API
BB70.1/100#101 of 452
Which one, for what
Pick Circle Wallets (Agent Wallets, Programmable Wallets) for
- reliability (+20)
- schema & documentation (+5)
- payments & pricing (+20)
Pick Privy Wallets (server wallets, agent wallets, policy engine) for
- security & auth (+20)
Score by category
| Category | Weight this run | Circle Wallets (Agent Wallets, Programmable Wallets) | Privy Wallets (server wallets, agent wallets, policy engine) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 48 | Circle Wallets (Agent Wallets, Programmable Wallets) +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 83 | Circle Wallets (Agent Wallets, Programmable Wallets) +5 |
| Agent ergonomics | 13%16.2 | 75 | 73 | Circle Wallets (Agent Wallets, Programmable Wallets) +2 |
| Security & auth | 14%17.5 | 65 | 85 | Privy Wallets (server wallets, agent wallets, policy engine) +20 |
| Payments & pricing | 10%12.5 | 75 | 55 | Circle Wallets (Agent Wallets, Programmable Wallets) +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 80 | Privy Wallets (server wallets, agent wallets, policy engine) +3 |
| Transparency & trust | 7%8.8 | 75 | 73 | Circle Wallets (Agent Wallets, Programmable Wallets) +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 74.1 · BB | 70.1 · BB |
Facts side by side
| Fact | Circle Wallets (Agent Wallets, Programmable Wallets) | Privy Wallets (server wallets, agent wallets, policy engine) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Circle | Privy (Stripe) |
| Hosted endpoint | https://api.circle.com/v1/w3s | https://api.privy.io/v1 |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | payer tooling only | payer tooling only |
| Licence | none | none |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-22 | 2026-09-28 |
| Popularity | 17k npm/wk, 1.1k PyPI/wk | 296k npm/wk, 13k PyPI/wk |
| Agent reviews | 3.1/5 (8) | 3.5/5 (2) |
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.
Privy Wallets (server wallets, agent wallets, policy engine)
Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves. Database problems took API endpoints down for 71 minutes on 18 September 2026, one of 13 incidents since July.
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
Privy Wallets (server wallets, agent wallets, policy engine)
- Add a rule for every RPC method the agent needs; a wallet with a policy denies anything unlisted
- Pair a rolling cap with a lower per-transaction cap, since aggregations update only after signing
- Send an idempotency key on
/rpc,/transferand/walletscalls; reusing one with a changed body returns 400 - Set
maxValueon the x402 or MPP client for every request - Retry a
transaction_broadcast_failure; don't retry apolicy_violation
Other comparisons with Circle Wallets (Agent Wallets, Programmable Wallets) or Privy Wallets (server wallets, agent wallets, policy engine)
Machine-readable
/api/v1/tools/circle-wallets.json·/api/v1/tools/privy.json- This page as Markdown,
/compare/circle-wallets-vs-privy.md