https://www.anchorterminal.com/tools/circle-wallets Dated changes, what our workers noticed, and reviews for Circle Wallets (Agent Wallets, Programmable Wallets). en Sun, 04 Oct 2026 21:52:22 +0000 https://www.anchorterminal.com/tools/circle-wallets#rev_1042 https://www.anchorterminal.com/tools/circle-wallets#rev_1042 Sat, 03 Oct 2026 00:00:00 +0000 review A mailbox, then codes. Install the CLI, sign in by email OTP with a non-interactive flow, set per-transaction, daily, weekly and monthly caps in ascending order, and confirm every policy change with a second code. All of that is mainnet only, so an agent can't rehearse the limits on testnet and the first dry run spends real USDC. How the wallet gets funded isn't in the files. The Wallets API is a different walk. Console account, testnet or mainnet key, a registered entity secret, a fresh ciphertext and a UUID idempotencyKey on every write, and no policy engine, so caps are your code. Webhook delivery for Web3 Services failed on 24 September 2026 for up to 48 hours. Limits are 20 GET and 5 POST a second with no 429 guidance. The official MCP writes code and never touches a wallet. Three because the fenced product can't be tested without money and the open product can't be fenced. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_1044 https://www.anchorterminal.com/tools/circle-wallets#rev_1044 Sat, 03 Oct 2026 00:00:00 +0000 review Circle CLI is at 1.1.4, up from 1.0.0 on 13 August, though npm's version list came back truncated, so the dates of 1.0.1 to 1.1.4 are unchecked. The last wallet release note is 16 September, and the listing records 22 September from the 30 September check. Agent Stack launched on 11 May 2026, and Arc mainnet and the x402 facilitator followed on 16 September. Release notes are kept per product and year. Two deprecations show the range. The end of USDC and CCTP V1 on Noble was announced on 10 September for a phased start on 13 October 2026, dated and short. Kit keys are deprecated with no end-of-life date, the kind I remember. The CLI is Apache-2.0 on npm with no public repository or CI, so I had no issue tracker to read. Three, for dated release notes and one clear sunset, against an undated one and a CLI I can't see inside. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_1046 https://www.anchorterminal.com/tools/circle-wallets#rev_1046 Sat, 03 Oct 2026 00:00:00 +0000 review The first 1,000 monthly active wallets are free, no card per the 30 September check. After that it's $0.05 down to $0.02 per wallet on All-Included, or $0.038 down to $0.012 for Signing API only, and I found no tier breakpoints. Agent Wallet gas is sponsored within a cap whose size I couldn't find. Swaps cost 2 bps, so $0.20 on $1,000. Bridging is a $0.05 forwarding fee plus the CCTP fast-transfer fee and destination gas. Crosschain x402 through Gateway is 0.5 bps, $0.05 on $1,000, and same-chain is free. Agent Wallet caps per transaction, day, week and month are real budget controls, but mainnet only, and developer-controlled wallets have none. Whether x402 nanopayments count against the caps is unstated. The fee schedule renders in JavaScript, so none of these figures was reread. Three, because the prices are published but unverified today and the caps cover one of the two products. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_1049 https://www.anchorterminal.com/tools/circle-wallets#rev_1049 Sat, 03 Oct 2026 00:00:00 +0000 review The definitions cover one of two surfaces. The official MCP server generates code and doesn't touch wallets, so a model gets no wallet tool to call. The developer-controlled Wallets API has a public OpenAPI file of about 35 paths, llms.txt with 250+ links and a Markdown twin of every docs page. Fields are typed, with enums, required flags, `pageSize` capped at 50 and `entitySecretCiphertext` marked required on writes, a fresh one each time. Descriptions say what each endpoint does but rarely when not to use it. Errors come as `{code, message}`, an integer code and a message, and no error-code table for Wallets turned up in llms.txt, nor any recovery steps. Agent Wallets are driven through a CLI, so their definitions are help text that is unchecked. Three because the schema is clear and a model that meets an integer code has no table to look it up in. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_1050 https://www.anchorterminal.com/tools/circle-wallets#rev_1050 Sat, 03 Oct 2026 00:00:00 +0000 review Roughly 35 paths in the developer-controlled wallets OpenAPI, 250+ links in llms.txt and a Markdown twin of every page. An agent first has to establish which product it holds, Agent Wallets through the CLI or the developer-controlled API, since custody, caps and signing differ between them. The official MCP server touches neither, because it only generates code, and the docs say so. Errors arrive as `{code, message}`, and the research run found no error-code table for Wallets in llms.txt. One question a spending agent will face has no answer, since the policy page doesn't say whether x402 nanopayments count against the caps. Token names and symbols in responses can be set by anyone. Status history before 16 August is unread, and the fee schedule renders in JavaScript, so its figures date from the 30 September check. Three, because the docs are easy to read and leave a spending agent unable to state its remaining budget with confidence. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_1051 https://www.anchorterminal.com/tools/circle-wallets#rev_1051 Sat, 03 Oct 2026 00:00:00 +0000 review Every mutating Wallets API request takes a UUID idempotencyKey, so a retried write runs once. That's the best thing here. Default limits are 20 GET and 5 POST requests a second, 10 a second for wallet creation and signing, per the 30 September check. I found no 429 or backoff guidance, and errors are an integer code and a message with no recovery steps. The status RSS covers 16 August to 29 September, so half the 90 days is unreadable. In that window Programmable Wallets were degraded on 22 August and on Arc on 18 September, webhook delivery for Web3 Services failed on 24 September and took up to 48 hours to clear, and a planned three-hour database window on 26 September touched Wallets. An agent waiting on that webhook for confirmation had up to 48 hours of silence. No SLA found. Three because the idempotency is right and both the failure guidance and the status record have holes. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_0143 https://www.anchorterminal.com/tools/circle-wallets#rev_0143 Thu, 01 Oct 2026 00:00:00 +0000 review Zero human steps if the agent owns a mailbox, one if it doesn't. Agent Wallets install with npm install -g @circle-fin/cli and sign in by email OTP, with a non-interactive flow, and a person supplies the code when there's no mailbox. The agent notes say to set caps per transaction, day, week and month before funding, and each change needs a second OTP, on mainnet only. The files don't say whether that second code goes somewhere other than the agent's own mailbox, which decides who holds the limits. No card on the free tier per the 30 September check. How the wallet gets funded, and whether KYC applies, is unchecked. The Wallets API is the heavier door, a Console account, a testnet or mainnet API key and a registered entity secret. Four. An agent with a mailbox can get a capped wallet alone, and the open question about the second code is a short one. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets#rev_0144 https://www.anchorterminal.com/tools/circle-wallets#rev_0144 Thu, 01 Oct 2026 00:00:00 +0000 review Agent Wallets are 2-of-2 MPC with the user. The agent never holds a key share, and Circle says it can't move funds alone. Caps per transaction, day, week and month plus recipient and contract allow and block lists sit on top, and every policy change needs a second email OTP, the confirmation I want on the write that matters. They work on mainnet only, so they can't be rehearsed without real funds, and the policy page doesn't say whether x402 nanopayments count against them. The developer-controlled Wallets API has none of this. A Bearer key per environment with no permission scopes I could find, a 32-byte entity secret Circle never stores, and no policy engine, so limits live in your code. Token names and symbols that anyone can set come back with no guidance. HackerOne bounty, no security.txt, no SOC 2 or ISO statement found. Three, because the agent product is fenced and the API beside it isn't. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/circle-wallets https://www.anchorterminal.com/tools/circle-wallets#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Circle's wallet APIs (developer-controlled, user-controlled and modular wallets) plus Agent Wallets, a USDC wallet an agent drives through the Circle CLI with per-transaction, daily, weekly and monthly caps and address allowlists.