Purpose & Value
OmniGENIE — Agentic Intelligence for Financial Operations (working title)
OmniGENIE is the working title for the newest component of the OmniOmni ecosystem, currently in active development: a controlled intelligence, memory and interaction layer for regulated financial operations. It is based on GENIE, the conversational memory and voice platform developed by Youki GmbH, and is being evaluated as a horizontal layer that connects people, conversations and the specialised OmniOmni components.
OmniGENIE is not a general-purpose chatbot and not an autonomous decision-maker. Its intended purpose is to make context available across cases and conversations, to prepare decisions, to coordinate approved working steps within explicit permissions, and to document sources, tool actions, approvals and outcomes in a way people can review.
What OmniGENIE is intended to do
- Operational memory: extract and retain typed, provenance-linked facts from conversations and case work, with a full revision history and controlled deletion.
- Voice and text interaction: real-time conversation with natural interruption, telephony (inbound and outbound calls, SMS) and structured call notes and follow-up tasks.
- Preparation, not execution: draft summaries, case files and next steps for a human decision; any write or transactional action in an OmniOmni component stays on the component's existing, authorised path.
- Traceability: log tool invocations with argument hashes and outcomes, record who approved what, and keep the assistant's own behaviour reviewable.
What OmniGENIE is not
OmniGENIE does not act as a crypto securities registrar, custodian, compliance officer, investment adviser or credit decision-maker, and it does not replace the people or licensed roles that hold these responsibilities. It prepares drafts and recommendations. It does not autonomously register securities, sign custody transactions, decide KYC cases, grant credit or give investment advice.
ecrop provides the OmniGENIE software. Licence-requiring activities — in particular crypto securities registration and crypto custody — continue to be performed exclusively by ecrop's licensed partners, who are supervised by BaFin.
Why ecrop is building OmniGENIE
Banks and regulated firms run digital-securities operations across many systems and conversations. Context gets lost between calls, cases and handovers; every clarification costs time; audit questions arrive months later. OmniGENIE is being built to close that gap inside the OmniOmni ecosystem:
- Institutional memory across cases. Facts, decisions and open items from conversations and case work stay available, with provenance and revision history, for the people authorised to see them.
- Controlled interaction channels. Voice, phone and text become disclosed, rule-bound entry points that record structured notes and route requests to the right team.
- Preparation instead of autonomous action. Summaries, case files and validated inputs are prepared by the assistant; every write into OmniAsset, OmniSafe or OmniEagle stays on the existing, authorised approval path.
- Traceability from day one. Sources, tool calls, approvals and outcomes are recorded as operational artefacts, without exposing internal model reasoning.
Development status
OmniGENIE is being integrated into the OmniOmni ecosystem now. The current development focus is the institutional foundation: institution-level tenant isolation, sign-in through the institution's identity provider, action tiers for observe, draft and recommend, structured log export, read integrations with OmniAsset and OmniEagle, and the handover of prepared actions to the Proof-of-Action approval in OmniPersona. The use cases show the sequence in which capabilities are released; Limitations & Availability lists what is not yet available. General availability will be announced; no dates are published here.
Shape OmniGENIE with us
Institutions that want to work with OmniGENIE early can join as design partners: jointly defining the first use cases, agreeing a pilot scope with exit criteria, and reviewing the control catalogue with their own risk, compliance and information-security functions. Contact ecrop to start the conversation.
Who this documentation is for
| Audience | What you will find |
|---|---|
| Banks and regulated financial firms | Control model, accountability, traceability, data protection, resilience and integration boundaries — see Security, Governance & Human Oversight. |
| Business and operations teams | Concrete relief in daily case work, the limits of the assistant, and where a human decides — see Financial Services Use Cases. |
| Developers and technology partners | Architecture, trust boundaries, memory model, deployment and the documented OmniOmni interfaces — see Architecture and OmniOmni Integrations. |
| Investors and strategic partners | The platform role of a horizontal intelligence layer above a modular digital-securities stack — described without market, revenue or customer figures. |
How to read the status labels
Every capability on the following pages carries one of four labels. Labels apply per capability, never to the product as a whole.
- Available
- Active in the productive GENIE platform today (technology basis).
- Implemented, not enabled
- Exists in code and tests, but is switched off or narrowly scoped in production.
- In development
- Being built now as part of the OmniGENIE integration into OmniOmni. Not yet generally available.
- Roadmap
- Planned for a later phase. Not available; no dates are published.
Explore OmniGENIE
Capabilities
What the underlying technology can do today, what exists but is not enabled, and what is in development.
Financial Services Use Cases
Five candidate use cases with workflow, human decision points, controls and pilot metrics.
Architecture
How context, memory, tools and approvals flow, and where the trust boundaries are.
Security, Governance & Human Oversight
Implemented controls, controls in development and the regulatory framing per use case.
Memory & Data Lifecycle
Provenance, revision history, sensitivity, correction, deletion and retention.
OmniOmni Integrations
Documented interfaces of each OmniOmni component and the OmniGENIE role in development.
Deployment & Operating Model
Current deployment topology, providers, configuration switches and institutional responsibilities.
Responsible AI, Limitations & Availability
Known limitations, transparency, non-roles and the phased plan without dates.
This documentation describes technical and organisational capabilities. It is not legal advice. The regulatory classification of any OmniGENIE use case depends on its intended purpose, the data processed, the decisions it informs and the governance of the deploying institution. Institutions should consult qualified legal counsel for their specific use case.