🇳🇱 NL

AI agent for ING NL API

Connect ING NL API to your AI agent through the WorkAist MCP server. NL banking

In 60 seconds

The WorkAist ING NL API connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write ING NL API data — banking — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.

Authentication & setup

The ING NL 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 ING NL API

FAQ

Can a WorkAist AI agent really automate ING NL 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 ING NL 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 ING NL 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 ING NL API's own API costs (if any) and the LLM tokens your agent consumes.

Is my ING NL API data sent to a third party?

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

What if ING NL API changes its API?

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

Source code on GitHub · Licensed under AGPL-3.0 · Self-hosted, your data stays yours.