Balances, transactions, fees and limits, answered from the bank's live record the moment the customer asks.
Transfers sent, deposits opened, cards blocked: executed in the core, with the customer's confirmation.
The repetitive share of daily volume, from statements to card blocks and status questions, resolved before it reaches a person.
Everything the bank needs to take agents into production and govern them there, from scope and audit to where the models run.
A modular catalogue: the bank switches agents on in its own order and adds the rest when it is ready.
The open standard for connecting AI to systems. Agents reach the core through it and see only the actions the bank exposes.
Scope set per agent, so what each agent may do is a decision the bank makes once.
SCA or biometrics on every execution, before anything reaches the core.
Every action, the customer and the rule behind it, written to the same audit trail as the rest of the core.
Tested banking actions built for this domain and reused by every agent that needs them.
iOS and Android, embedded into any mobile banking app, whoever built it.
Open-weight models on the bank's own infrastructure, or the bank's own provider key.
AI agents that complete banking tasks inside the bank's own app. Where an assistant answers, an agent prepares the payment, opens the deposit or blocks the card, then hands the customer the confirmation step.
A chatbot answers from a script or a knowledge base. An agent reads the customer's own data from the core and executes the action once the customer confirms.
No. Retrieval is one part of it: answers come from the bank's live record, and actions run through tested banking skills in the core.
RPA replays fixed clicks on screens. Agents understand the request, work through the actions the bank exposes over MCP and stop for confirmation before anything executes.
The open standard for connecting AI to systems. Agents reach the core through it and receive only the actions the bank chooses to expose.
Scope is set per agent, every execution requires SCA or biometrics, transfers pass Verification of Payee and every step is written to the verification diary.
On the bank's own infrastructure or in its cloud. With open-weight models on the bank's infrastructure, no third party sits in the chain and customer data stays inside the bank's environment.
No. The SDK embeds into any mobile banking app, and the adapter connects to any core.
Yes. The catalogue is modular: the bank switches agents on in the order it chooses and adds the rest later.
