Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Commerzbank PSD2 Open Banking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcommerzbank.com%2Fcommerzbank" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcommerzbank.com%2Fcommerzbank" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Commerzbank PSD2 Open Banking API.
List the customer's accounts and read the details of one account
Read the balances and transactions for an account
Create an access consent and check or delete it
Start and manage consent authorisations
Initiate a payment and read or cancel its status
GET STARTED
Confirm whether funds are available for an amount
Patterns agents use Commerzbank PSD2 Open Banking API for, with concrete tasks.
★ AI agent account aggregation
An AI agent reads balances and transactions across the accounts a customer has consented to share, so a reporting workflow can categorize spending. Through Jentic the agent finds the account-information operations by intent and calls them within the active consent, without hand-building the Berlin Group headers.
List the consented accounts and return the last 30 days of transactions for each
Payment initiation
A payment workflow initiates a transfer for a chosen payment product and then polls the payment status until it settles or is rejected. The API separates initiation from status so the workflow can confirm the outcome before notifying the customer.
Initiate a SEPA credit transfer and poll its status until it is accepted
Funds confirmation
Before charging a customer, a merchant checks whether the account holds enough for the amount using the funds-confirmation endpoint. The API returns a yes or no answer under the customer's consent, so the debit can proceed only when funds are present.
Confirm whether a consented account has at least the required amount available
19 endpoints — the commerzbank psd2 open banking api provides berlin group access to commerzbank accounts under psd2: it lists accounts, reads balances and transactions, manages access consents, initiates payments, and confirms funds availability.
METHOD
PATH
DESCRIPTION
/berlingroup/v1/accounts
List accounts
/berlingroup/v1/accounts/{account-id}/balances
Get account balances
/berlingroup/v1/accounts/{account-id}/transactions
Get account transactions
/berlingroup/v1/consents
Create an access consent
/berlingroup/v1/payments/{payment-product}
Initiate a payment
/berlingroup/v1/funds-confirmations
Confirm funds availability
/berlingroup/v1/accounts
List accounts
/berlingroup/v1/accounts/{account-id}/balances
Get account balances
/berlingroup/v1/accounts/{account-id}/transactions
Get account transactions
/berlingroup/v1/consents
Create an access consent
/berlingroup/v1/payments/{payment-product}
Initiate a payment
/berlingroup/v1/funds-confirmations
Confirm funds availability
What agents get from Jentic-routed access to this vendor.
Setup
Calling the Commerzbank PSD2 API by hand means running the OAuth2 authorization-code flow with the right ais, pis, or fcs scope, creating a consent, and following the Berlin Group headers on every call. Through Jentic you install once, import the API, connect your OAuth2 credential, and your agent calls it.
Permission scoping
The account id, consent id, and payment id sit in the URL path, so a rule can allow your agent to read balances and transactions while blocking payment initiation and consent deletion. You choose the operations it may call, so money-moving requests are excluded unless you add them.
Credential isolation
Your Commerzbank OAuth2 credential is stored once, encrypted, by your own Jentic One instance and injected when the agent runs. It never appears in the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read account transactions' or 'initiate a payment', and Jentic returns the matching Commerzbank operation with its input schema so the agent calls the right endpoint without parsing the Berlin Group spec.
Alternatives and complements available in the Jentic catalogue.
Specific to using Commerzbank PSD2 Open Banking API through Jentic.
Is there a Commerzbank PSD2 MCP server?
You don't need an MCP server to connect your agent to the Commerzbank PSD2 API. Jentic connects it directly from the API Directory: import the API, connect your OAuth2 credential, and your agent reads accounts and initiates payments on demand.
Can I limit what my agent is allowed to do with the Commerzbank PSD2 API?
Yes. Write a rule that allows only the account-information reads, so the agent can pull balances and transactions but cannot initiate a payment or delete a consent. The account and payment ids travel in the URL path, and every call the agent makes is logged.
What authentication does the Commerzbank PSD2 API use?
The Commerzbank PSD2 API authenticates with OAuth2 using the authorization-code flow and PSD2 scopes, per its OpenAPI spec. Through Jentic the OAuth2 credential is stored once by your self-hosted instance and injected at call time, so it never reaches the agent's context.
Can I read a customer's transactions with the Commerzbank PSD2 API?
Yes, once the customer has granted a consent. Create the consent, have it authorised, then read the account list and the balances and transactions for each account within the consent's scope.
What are the rate limits for the Commerzbank PSD2 API?
The OpenAPI spec does not specify rate limits. PSD2 rules cap unattended account access to a limited number of calls per day, so check Commerzbank's developer terms before scheduling frequent syncs.
How do I connect the Commerzbank PSD2 API to my AI agent?
Search the Jentic API Directory for the Commerzbank operation you need, such as reading account transactions, and import it. To run it on your own infrastructure, install Jentic One from its GitHub repo, then your agent calls the API with your OAuth2 credential injected at execution time.
For Agents
List Commerzbank accounts, read balances and transactions, create and manage access consents, initiate payments, and confirm funds availability under the PSD2 Berlin Group standard.
Use for: List the accounts a customer has consented to share, Read the recent transactions on an account, Create a consent to access account information, Initiate a SEPA payment
Not supported: Does not open accounts, issue cards, or serve retail customers directly; it is a PSD2 third-party-provider interface requiring a valid consent. Use for Commerzbank account information, consents, payments, and funds confirmation only.
The Commerzbank PSD2 Open Banking API provides Berlin Group access to Commerzbank accounts under PSD2: it lists accounts, reads balances and transactions, manages access consents, initiates payments, and confirms funds availability. Use it to build account-information and payment-initiation flows against Commerzbank as a licensed third-party provider.