Allocate a pocket
Keep agent spending separate from the main balance. Fund the dedicated account through an owner-authorized workflow.
PLATFORM / AGENTIC BANKING
Agentic banking.
Your institution.
Your rules.
Give AI agents dedicated accounts and defined authority - with the bank in control of how money moves.
FOR BANKS, CREDIT UNIONS & FINTECHS
agora / agenticILLUSTRATIVE
Customer’s main account$12,000.00
Owner controlledOwner-authorized allocation
Dedicated agent pocket
Defined mandateHousehold assistant
$300.00Allocated budget
Per purchase$75 limit
Above $50Approval required
Authority stays with the account owner.
A NEW BANKING INTERFACE
The largest banks are restricting agents.
Build a controlled alternative.
The largest banks have been reported to block or limit external AI agents’ access or transaction initiation.
The concern is understandable: shared banking credentials can give software far more authority than a task requires. Local institutions have an opportunity to offer useful automation through a defined, bank-controlled access model.
THE OPEN BANKING PRECEDENT
Open banking has already shown how third-party data access can be restricted and subsequently governed by new agreements with a fee structure. Access continued - on negotiated terms. Agentic banking could follow a similar path.
DEDICATED FUNDS. EXPLICIT AUTHORITY.
A product your customers
can understand and control.
“Set aside $300 for your assistant. Choose where it can spend, set a purchase limit, and decide when it must ask you first.”
Define the mandate
Specify approved actions, merchants, budgets, expiration, and when customer confirmation is required.
Control execution
Validate every instruction against the mandate, available funds, and the institution’s operating rules.
The customer or business owns the funds. The agent acts as a software delegate. Account isolation must also control overdrafts, fallback funding, and automatic replenishment.
THE AGORA FOUNDATION
“We have APIs”
is only the beginning.
The infrastructure behind the API determines what an agent can safely do.
An API can expose a balance. The ledger determines whether it reflects holds, concurrent requests, and available funds. An API can accept a payment instruction. The execution controls determine whether it should proceed.
Explore our side-core approach01
Real-time multi-ledger
Distinct balances, account allocations, and clear accounting boundaries.
02
Event-driven microservices
Modular account, payment, card, and identity services that can evolve independently.
03
Programmable banking
Subaccounts, shared pockets, transfers, cards, and transaction visibility.
04
Modernize around your core
Build new experiences alongside existing systems, with explicit integration and reconciliation.
BUILT AROUND REAL CUSTOMER NEEDS
One foundation.
Multiple agentic experiences.
EVERYDAY AUTOMATIONDelegate the routine.
Delegate the routine.
Keep the boundaries.
Let an assistant prepare or request everyday purchases within a dedicated household budget, with clear limits and customer confirmation.
EXAMPLE MANDATE
- Allocated pocket$300
- Purchase ceiling$75
- Above $50Customer approval
- FundingNo automatic top-up
Illustrative use cases. Deployment scope is defined with the institution and its banking and payment partners.
AUTHORITY BY DESIGN
The agent requests.
The bank-controlled services decide.
Combine Agora’s existing account and payment foundation with an additional agent-specific control layer for registration, delegated credentials, mandate enforcement, and coordinated revocation.
The model never receives the customer’s banking password or a platform-wide credential. MCP or REST can expose a limited set of tools through the same controlled gateway.
01
Customer & registered agent
A specific mandate, identity, account, and purpose.
02
Delegation & policy
Permissions, budgets, destinations, approval, and expiration.
03
Controlled execution
Atomic reservations, duplicate protection, and status checks.
04
Agora banking services
Accounts, ledger, money movement, and payment instruments.
05
Institution & payment rails
Defined accounting ownership, authorization, and settlement.
Evidence across the lifecycle Customer authority → policy decision → reservation → execution → reconciliation.
REAL-TIME CONTROL
A balance check
isn’t enough.
Two simultaneous $70 requests can both pass a balance check against a $100 pocket. An execution service must reserve funds and budget capacity atomically.
Our approach requires controls that remain consistent across agents, sessions, and payment channels.
ILLUSTRATIVE MONTHLY BUDGET
Authorized cap$300
Committed spend$160
Active reservations$80
Remaining authority$60
$70 purchase requestOutside budget
committed + reserved ≤ authorized capTransaction-bound approval
Bind confirmation to the actual amount, destination, account, and expiration.
Revocation at execution
Stop new instructions under revoked authority. Handle already dispatched payments under rail-specific rules.
Reconstructable evidence
Connect mandate versions, decisions, postings, and processor outcomes through settlement.
BUILT FOR DEVELOPERS
Concrete banking APIs.
A clear implementation path.
Inspect the documented services behind account creation, funding, shared payments, and spending instruments.
Explore the API catalog| Capability | Documented endpoint | Role |
|---|---|---|
| Internal accounts | POST /users/{user_id}/accounts | Dedicated funding pockets |
| Balances | GET /users/{user_id}/accounts/{account_id}/balance | Account balance visibility |
| Internal transfers | POST /users/{user_id}/accounts/{account_id}/transactions/internal | Owner-authorized funding |
| Shared pockets | POST /users/{user_id}/account/share-pocket | Shared funding arrangements |
| Shared payments | POST /users/{user_id}/accounts/{account_id}/transactions/splitBill | Split-payment workflows |
| Card issuance | POST /users/{user_id}/accounts/{account_id}/cards/issue | Eligible spending instruments |
| Card restrictions | POST /users/cards/setMerchantRestriction | Supported merchant restrictions |
| Card blocking | POST /users/cards/block | Instrument suspension |
Paths are relative to the /v2 base. Available operations and controls depend on the institution’s program, processor, and integration.
How is an agent mandate represented?
Translate natural-language instructions into a structured mandate with an owner, registered agent, allowed actions, funding account, merchant restrictions, budget, and expiration.
This illustrative policy describes the proposed agent-control layer. It is not an existing Agora API request. Amounts shown use USD cents.
{
"agent_id": "agent_household_001",
"account_id": "pocket_001",
"currency": "USD",
"allowed_actions": ["purchase.intent.create"],
"per_purchase_limit_minor": 7500,
"calendar_month_cap_minor": 30000,
"approval_required_above_minor": 5000,
"automatic_replenishment": false,
"external_transfers_allowed": false,
"policy_version": 3,
"status": "ACTIVE"
}What protects against duplicate payments and prompt injection?
Durable idempotency records and authenticated callbacks prevent retries or repeated events from becoming duplicate payments. Timeouts require inquiry and reconciliation before resubmission. A request_id field alone does not establish this guarantee.
A website, invoice, or model response cannot enlarge the stored mandate. The institution-controlled service validates identity, account, destination, amount, budget, and approval before execution.
How does Agora’s approach protect bank-controlled data?
Preserve institution-specific data boundaries and bank-controlled access, with US data residency forming part of the design for US institutions. Define what agents can read, what model providers receive, and how prompts, logs, backups, and telemetry are handled.
Model-training permissions and operational access must be explicitly agreed. Data residency and logical isolation form part of the control framework; broader sovereignty requires contractual and operational controls.
How does agentic banking fit alongside an existing core?
Agora’s modular side-core approach adds real-time account structures, programmable balances, and new customer experiences alongside existing infrastructure. The integration defines the authoritative system for each balance and event.
If the core maintains the deposit liability while a side ledger allocates pockets, holds, clearing, fees, and settlement must reconcile without double-counting funds. The same foundation can support teen, family, SMB, and embedded-fintech programs.
TAKE CONTROL OF YOUR ROADMAP
Your next banking experience.
Built with Agora.
Define your first agentic use case. Connect it to your banking environment. Build a controlled deployment around your customers.
Let’s talk agentic bankingThe customer sets the mandate.
The bank enforces the boundary.
The agent works within it.