AI agent for SEB Latvia API

Connect SEB Latvia API to your AI agent through the WorkAist MCP server.

/ agents/marketplace

Marketplace

Pre-built connector templates · install with one click.

Connector
SEB Latvia API
Production-grade banking MCP server. AGPL-3.0, self-hosted.
v1.2.8bankingoauth
  1. 1Install in one click

    Pick SEB Latvia API from the marketplace. WorkAist handles OAuth 2.0 and stores the credentials encrypted — no JSON keys to paste.

  2. 2Tools auto-generated

    SEB Latvia API exposes 6 MCP tools to every agent in your workspace: list_accounts, get_balance, list_transactions, create_transfer, and more. Each tool is a typed function, not a brittle script.

  3. 3Data flows to your graph

    Historical banking records sync to your private knowledge graph. Agents query relationships across all connected sources, not just SEB Latvia API in isolation.

  4. 4Your agents take action

    Your AI agent picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every SEB Latvia API call.

In 60 seconds

SEB Latvia API is banking software built for businesses in Latvia you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents categorise transactions, reconcile accounts and prepare reports — autonomously, under explicit permissions, with no manual hand-offs. SEB Latvia API authenticates via OAuth, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.

Authentication & setup

The SEB Latvia API connector authenticates via OAuth 2.0.

One-click OAuth setup

WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.

Frequently paired with SEB Latvia API

FAQ

Can a WorkAist AI agent really automate SEB Latvia API end-to-end?

Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.

How does this differ from using the SEB Latvia API API directly?

The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents SEB Latvia API as part of a unified Knowledge Graph alongside your other tools.

What does it cost?

WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for SEB Latvia API's own API costs (if any) and the LLM tokens your agent consumes.

Is my SEB Latvia API data sent to a third party?

No. WorkAist runs in your own infrastructure. Data flows from SEB Latvia API → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.

What if SEB Latvia API changes its API?

The connector is versioned and published openly. When SEB Latvia API ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.

Licensed under AGPL-3.0 · Self-hosted, your data stays yours.