Software that selects a service can also become the customer paying for it. Coinstancy is building around that shift with Coinstancy Agentic Bank, announced for November 16, 2026. The service brings together USDC wallets for AI agents, owner-defined payment policies and hosted workflows that can continue after an assistant session ends.
The product addresses a practical question for businesses adopting agents: how does software buy the information or service it needs without receiving unrestricted access to company funds? A model can identify a useful tool, but choosing that tool and having permission to pay for it are separate decisions.
Coinstancy places the financial decision alongside the task. An owner assigns a wallet and sets the conditions under which an agent can spend. The agent can then purchase compatible services through x402, with receipts and activity records available for review.
Buying a resource when the task needs it
For an API provider, the commercial opportunity is a purchase initiated by software at the moment a resource becomes useful. A research agent might need one market-data response to finish a brief. A monitoring process might need another source when an event occurs. The demand is attached to the task rather than necessarily to an ongoing subscription.
x402 gives compatible services a way to communicate payment requirements within a web interaction. When software requests a paid resource, the service can return the terms needed to obtain it. Payment can then form part of accessing that resource, subject to the permissions of the wallet making the purchase.
Coinstancy’s public product page describes dedicated agent wallets funded with USDC on Base. USDC is a stablecoin designed to track the US dollar. Here, its role is payment for a digital service: the cost belongs to the workflow and can be reviewed alongside the request that produced it.
That arrangement connects two business decisions. The provider decides what access costs and which payment conditions it accepts. The operator decides which services its software is allowed to buy and how much of a task’s budget can go towards those purchases.
For providers, per-request access offers a way to serve occasional demand as well as regular users. An agent may need a narrowly defined result from a service it does not use every day. Making that result purchasable during the task can broaden the situations in which paid data becomes useful.
Delegation starts with the owner’s rules
Coinstancy’s spending controls include transaction limits, daily and monthly budgets, approved services, price limits and thresholds for human approval. These settings define the authority assigned to each agent. Autonomous purchases are confined to the agent’s separate wallet rather than extending to the owner’s main account.
The distinction becomes relevant when a workflow makes several purchases. A small individual expense may fit within a transaction limit while repeated calls approach the daily allowance. The operator needs rules that apply across the task, as well as a way to identify purchases that deserve a person’s attention.
For example, a team preparing a recurring industry briefing could permit selected data services within an allocated budget and require approval above a chosen threshold. The policy establishes the financial scope before the agent starts looking for resources. The model’s assessment that a source would be helpful does not itself expand that authority.
The product page also describes revocable access, a simulation mode enabled by default and the ability to pause paid calls. Receipts and activity records give the operator material to inspect after execution. Those records help connect an expense to the work that prompted it, rather than leaving payment history detached from the agent’s task.
Personal assistants and agent wallets serve different roles
Coinstancy separates delegated purchasing from its Personal MCP connection. MCP, the Model Context Protocol, links compatible AI clients with external tools. Through the personal connection, an assistant can work with portfolio information, transactions, rates and investments associated with the user’s account.
In that personal flow, each financial action requires explicit confirmation after a quote or estimate. The assistant helps a person examine information and prepare an action. A separate agent wallet supports a different arrangement: purchases can proceed inside an authority that the owner has already defined.
For a business, the choice depends on the work being delegated. A person reviewing a proposed financial action may want to approve each step. A recurring data task may instead call for a limited allowance and an approved group of services. Keeping those modes distinct makes the relationship between account access and purchasing authority clearer.
Execution beyond the conversation
Cloud Run adds hosted execution to the wallet model. Coinstancy describes workflows that begin on a schedule or in response to an event and continue after the AI client disconnects. The owner does not have to keep a conversation open for the task to remain active.
This shifts the use case from a single assisted purchase to an ongoing process. A scheduled monitoring workflow can request information, process it and record the associated spending across successive runs. Wallet policies and cost limits continue to apply to the paid steps, while approvals and pausing remain part of the operating model.
For operators, persistent execution makes the budget an ongoing management decision. A useful workflow may run repeatedly, drawing on the same allowance over time. Daily and monthly limits give the owner a frame for that recurring expenditure, while approval thresholds identify the purchases that should return to a person for review.
Bringing execution and payments together also changes what an operator reviews. The relevant unit is the whole workflow, including the resources it requested and the expenses attached to them. A payment receipt explains a purchase; the activity history provides the surrounding context of the task.
The product therefore combines three roles: a connection for personal account tools, a bounded wallet for delegated purchases and an execution environment for recurring work. The November 16 launch puts that combination in front of developers and businesses deciding how agents should obtain and pay for external services.
Its commercial proposition is a practical one: let software buy the digital services an authorised task needs, while keeping the owner’s budget, permissions and review process attached to the work.
Media contact
Armand Bouchard, Founder & CEO, Coinstancy
armand@coinstancy.com | +33 6 33 18 05 11