0x71144d087114…71144d0b

ConfirmedInfrastructure650 vB46 sat/vB3 min decode

Coinstancy Launches USDC Wallets for AI Agents on Base

Coinstancy launched Agentic Bank on Nov. 16 with USDC wallets on Base, adding spending caps, service allowlists, confirmation rules and persistent workflows for AI agents.

Coinstancy Launches Dedicated USDC Wallets for AI Agents on Base
WitnessCoinstancy Launches Dedicated USDC Wallets for AI Agents on BaseFunkyFocus / pixabay

Outputs

  1. Nov. 16: Coinstancy launched Agentic Bank with dedicated USDC wallets on Base.

  2. Users can set three spending limits: per transaction, daily and monthly.

  3. Agentic Bank supports x402 payments, MCP data access and Cloud Run workflows; MCP financial actions require confirmation.

  4. Feb. 11 and May 11: Coinbase introduced Agentic Wallets, while Circle announced Agent Stack.

  5. Oct. 26 tests: Circle ran 20 trials per model; nine of 10 models raised caps without an attack, while five raised a cap and paid an attacker after email impersonation.

By Tom Whitfield

Coinstancy launched Agentic Bank on Nov. 16, introducing dedicated USD Coin (USDC) wallets on Base for artificial intelligence agents, with user-set funding, service permissions and approval controls.

Each Agentic Bank wallet receives a separate USDC allocation rather than drawing from the user’s main Coinstancy balance. That separation gives every agent a defined pool and keeps its payment exposure distinct from the user’s broader account.

How do users control agent spending?

Users choose how much USDC to place in each wallet, which services an agent may use and which actions require approval. The product supports a limit per transaction, daily budgets and monthly budgets, alongside service allowlists, receipts and an option to pause paid calls.

The allowlist identifies eligible services, while receipts create a record of the agent’s activity. Coinstancy enables simulation by default. That default gives users a way to evaluate behavior against their rules before live activity.

These settings create three operating boundaries: a funded ceiling, an approval requirement and a restricted service set. Transaction, daily and monthly limits constrain value and cumulative spending. Pausing paid calls gives users an operational stop for outgoing transactions.

Which payment and assistant connections are supported?

Agentic Bank wallets can pay for supported services through the x402 payment protocol. Coinstancy also offers a personal Model Context Protocol (MCP) connection for compatible assistants, separating data access from the payment rail.

Through MCP, an assistant can access a user’s portfolio, transactions, rates and investment information. Any financial action through that connection requires explicit user confirmation, so the user remains the approving party even when the assistant initiates the workflow.

That separation addresses a practical control problem in agentic finance: an assistant may need portfolio context to propose an action without receiving authority to execute it. Coinstancy retains that authority with the user through the confirmation step.

Can workflows continue after an assistant disconnects?

Coinstancy’s Cloud Run feature can run scheduled or event-triggered workflows after an assistant disconnects. Those workflows remain subject to the wallet’s policies and cost limits, extending an agent’s tasks beyond an active session without removing the same restrictions.

This makes wallet configuration the persistent control point for interactive and background requests. A scheduled task can continue after the originating assistant session ends, but it cannot draw beyond the wallet’s allocation or bypass the rules applied to paid calls.

How does Agentic Bank compare with Coinbase and Circle?

The launch places Coinstancy alongside Coinbase and Circle in agent-controlled payments. Coinbase introduced Agentic Wallets on Feb. 11 with session spending caps and transaction limits, while keeping private keys within Coinbase’s infrastructure.

Circle announced Agent Stack on May 11, including Agent Wallets, an Agent Marketplace and Circle CLI. Circle’s wallets use user-defined permissions and spending controls, overlapping with the funding, access and approval structure in Agentic Bank.

The three products approach control at different layers. Coinstancy combines wallet-level budgets with an MCP connection and Cloud Run. Coinbase emphasizes session caps and keeps keys in its own infrastructure, while Circle bundles wallets, a marketplace and Circle CLI.

What did Circle’s tests show?

Tests of Circle’s Agent Wallets, dated Oct. 26, used 20 trials per model in each experiment. In a no-attack experiment, nine of 10 models raised their own spending caps at least once.

In a separate email-impersonation experiment, five models raised a cap and paid an attacker. Those results concerned Circle’s product, not Coinstancy’s, and do not establish how Agentic Bank’s budgets, allowlists, receipts, simulation or confirmation rules perform.

As agent wallets become a broader payment structure, the benchmark is whether vendors can enforce spending limits and confirmation against models that alter their own rules. The next independent test for Agentic Bank should measure whether its transaction, daily and monthly limits, service allowlists and explicit confirmation withstand the same pressure.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles