Home / Integrations

Works alongside the systems you already run.

Tuvel connects to your core, loan, CRM and KYC systems rather than replacing them, over connections your security team can check.

How a system connects.

Every connection becomes tools in the console, granted one agent at a time.

  • Import an OpenAPI description

    Load the description of a bank API, and each operation becomes a tool you can grant.

    Available now

  • Connect an MCP server

    Point Tuvel at an MCP server, and its tools appear in the console, ready to grant.

    Available now

  • Your core’s own MCP skills

    Where your core banking vendor offers MCP skills for its core, Tuvel can use them directly, granted to one agent at a time like any other connector.

    Per deployment

  • Connector templates

    Templates for common bank systems, so a new connection starts from a ready shape.

    Available now

  • Granted per agent

    A connector is granted to one agent at a time, scoped to what it needs, and revoked in one click.

    Available now

Every connection, secured.

How calls reach your systems, and how changes to them are controlled.

  • Mutual TLS

    Calls to a bank’s APIs over mutual TLS, so each side proves who it is.

    Available now

  • Signed requests

    Each request is signed, so the bank’s system can check it came from Tuvel unchanged.

    Available now

  • OAuth

    For bank APIs that use OAuth, Tuvel connects with OAuth.

    Available now

  • One fixed outbound IP

    Calls leave from one fixed IP address your network team can allowlist.

    Available now

  • No inbound ports

    An on-premises relay lets agents reach internal systems without a port opened to the internet.

    Per deployment

  • Maker-checker and a tamper-evident trail

    Two-person approval for changes to connections, and every call to a bank system in a hash-chained trail.

    Available now

KYC checks at source.

Connector specs for verifying identity, tax and company records at their source. Each field the KYC agents fill records which source verified it, with its reference and time.

Per deployment

The KYC and onboarding desk

  • PAN
  • Central KYC (CKYC)
  • GSTIN
  • Company registry
  • Legal Entity Identifier (LEI)
  • Account name look-up
  • DigiLocker
  • Sanctions lists

What it plugs into.

Categories of the systems a bank runs. Each connector is built for your systems during the pilot.

  • Core banking

    Balances, transactions, transfers and servicing changes.

    Connector built per pilot

  • Loan origination and management

    Applications, files, sanction conditions and disbursement.

    Connector built per pilot

  • CRM

    Customer and client records, tasks and relationship history.

    Connector built per pilot

  • KYC, CKYC and credit bureau

    Identity, KYC refresh, bureau reports and scores.

    Connector built per pilot

  • Payments

    UPI, NEFT, RTGS, IMPS, SWIFT, cards and bill payments.

    Connector built per pilot

  • Account Aggregator

    Consent-based account data for advice and underwriting.

    Connector built per pilot

  • Document stores

    Loan files, policies, circulars and correspondence.

    Connector built per pilot

  • Treasury and markets data

    Positions, rates, funds and market data.

    Connector built per pilot

  • Contact centre and messaging

    Call transcripts, chat, email and messaging channels.

    Connector built per pilot

Your knowledge, loaded: policies, product documents, circulars and procedures go into the knowledge base every agent reads.

Questions.

How do we connect a system to Tuvel?

Import its OpenAPI description or connect its MCP server. Each operation or tool appears in the console, and you grant it to one agent at a time, scoped to what that agent needs.

Can Tuvel use our core banking vendor’s MCP skills?

Yes. Where your core vendor offers MCP skills for its core, Tuvel can use them directly, granted per agent like any other connector. We set this up with you in the deployment.

How are connections secured?

Over mutual TLS, with each request signed, or through OAuth, from one fixed outbound IP address you can allowlist. Changes to connections need two people, and every call to a bank system is kept in a tamper-evident, hash-chained trail.

Do we have to open inbound ports?

An on-premises relay lets agents reach internal systems without a port opened to the internet. It is set up for each bank in its deployment.

Which KYC checks have connector specs?

PAN, Central KYC, GSTIN, company registry, LEI, account name look-up, DigiLocker and sanctions lists. Each is set up with the provider your bank chooses, as part of its deployment.

Map your systems with us.

We list the systems the first desk needs and how each one connects.

Book a 30-min walkthroughPick a time (opens the booking calendar in a new tab)

Or write to demo@tuvel.co.