AI agent for KBC API
Connect KBC API to your AI agent through the WorkAist MCP server.
Marketplace
Pre-built connector templates · install with one click.
- 1Install in one click
Pick KBC API from the marketplace. WorkAist handles OAuth 2.0 and stores the credentials encrypted — no JSON keys to paste.
- 2Tools auto-generated
KBC 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.
- 3Data flows to your graph
Historical banking records sync to your private knowledge graph. Agents query relationships across all connected sources, not just KBC API in isolation.
- 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 KBC API call.
KBC API is banking software built for businesses in Belgium 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. KBC API authenticates via OAuth, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.
Authentication & setup
The KBC API connector authenticates via OAuth 2.0.
WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.
Frequently paired with KBC API
FAQ
Can a WorkAist AI agent really automate KBC 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 KBC 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 KBC 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 KBC API's own API costs (if any) and the LLM tokens your agent consumes.
Is my KBC API data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from KBC API → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if KBC API changes its API?▼
The connector is versioned and published openly. When KBC API ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.