Install Jentic One Beta

Connect the BankIntegration Erp API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BankIntegration Erp 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%2Fapi2.bankintegration.dk%2Fbankintegration" | sh

Step 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%2Fapi2.bankintegration.dk%2Fbankintegration" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with BankIntegration Erp API.

Provision customer companies and refresh their details from the Danish CVR register

Manage platform users and their access to a company's bank agreements

Create and update bank agreements that authorize payment exchange

Resolve the accounts covered by a specific agreement

Validate payment routing against reference lists of banks and bank centrals

GET STARTED

Start building with BankIntegration Erp API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BankIntegration Erp API for, with concrete tasks.

★ Onboard ERP customers into BankIntegration

Accounting and ERP software vendors set up each client company before payments can be exchanged. The BankIntegration ERP API creates the company, enriches it from the Danish CVR business register, and attaches the users who will administer it, so a vendor can provision a new customer without manual data entry.

Create a company record, refresh it from the CVR register, then create an administering user for that company.

Set up bank agreements for payment exchange

Before a customer can send or receive payments a bank agreement must exist. The API creates agreements of the correct type, updates them as the relationship changes, and lists the accounts each agreement covers, giving an integration a complete view of a customer's banking setup.

Create an agreement of a chosen type for a company and list the accounts attached to it.

Validate payment reference data

Cross-border payments fail when bank, country, or currency details are wrong. The API exposes canonical reference lists for banks, bank centrals, countries, and currencies so an integration can confirm routing information before it creates or updates an agreement.

Fetch the list of banks and currencies and confirm a target bank and currency are supported before creating an agreement.

Automate customer setup from an AI agent

An AI agent handling vendor onboarding can drive the whole BankIntegration setup: it reads reference data, creates the company and its users, enriches from CVR, and opens the required agreements. Through Jentic the agent discovers these operations by intent and runs them in sequence under the vendor's own credentials.

Given a company registration number, create the company, refresh it from CVR, add an admin user, and create a default agreement.

Key Endpoints

26 endpoints — the bankintegration erp api lets accounting and erp software vendors administer their own customers inside the danish bankintegration platform.

METHOD

PATH

DESCRIPTION

POST

/company

Create a customer company

POST

/company/{id}/updateFromCvr

Refresh company data from the Danish CVR register

POST

/user

Create a platform user

GET

/agreements

List bank agreements

POST

/agreements

Create a bank agreement

GET

/agreement/{id}/accounts

List the accounts covered by an agreement

GET

/banks

List supported banks

POST

/company

Create a customer company

POST

/company/{id}/updateFromCvr

Refresh company data from the Danish CVR register

POST

/user

Create a platform user

GET

/agreements

List bank agreements

POST

/agreements

Create a bank agreement

GET

/agreement/{id}/accounts

List the accounts covered by an agreement

GET

/banks

List supported banks

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring up BankIntegration by hand means handling its subscription-key header, the CVR refresh step, and the agreement-then-accounts sequence yourself. With Jentic you install once, import the API from the Directory, and store the subscription key a single time.

Permission scoping

Because Jentic runs inside your own instance, you decide which operations the agent may call, so you can keep it to reads on companies, agreements, and accounts while blocking writes. Access is granted per operation.

Credential isolation

Your subscription key is held encrypted by your own Jentic One instance and injected only when an operation runs, so it never appears in the agent's prompt, logs, or context.

Intent-based discovery

Agents find BankIntegration through Jentic's intent search: a request like provision a customer company or list accounts for an agreement resolves to the right operation with inputs and auth prepared.

FAQs

Specific to using BankIntegration Erp API through Jentic.

Is there an MCP server for the BankIntegration API?

You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call BankIntegration operations directly by intent, so you connect the API without maintaining separate MCP tooling.

Can I limit what my agent is allowed to do with the BankIntegration API?

Yes. Because you run Jentic yourself, you choose which BankIntegration operations your agent can call, so you can allow reference lookups and company reads while withholding agreement or user changes. Scoping is applied per operation.

What authentication does the BankIntegration API use?

The BankIntegration API is protected by a subscription key. You pass it in the `Ocp-Apim-Subscription-Key` request header or as the `subscription-key` query parameter, and Jentic supplies it from your stored credential when an operation runs.

Does the BankIntegration API move the actual payments?

No. It administers customers, users, agreements, and accounts and exposes banking reference data. Moving funds happens through the agreements it sets up, not through these endpoints.

What reference data can the agent read?

The agent can read canonical lists of banks, bank centrals, countries, and currencies, plus individual records by identifier, which lets it validate routing details before creating or updating an agreement.

How does an agent discover BankIntegration operations in Jentic?

The agent searches Jentic by intent, such as creating a company or listing accounts for an agreement, and Jentic returns the matching BankIntegration operations ready to run under your credentials.

Api2 Bankintegration Dk BankIntegration Erp API

Name: BankIntegration Erp API
Brand: BankIntegration ERP API
Availability: InStock

Community OpenAPI document · agent-readyFinanceBankingapiKey26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Lets an AI agent provision ERP customer companies, users, and bank agreements in the BankIntegration platform and read reference data on banks, countries, and currencies.

Use for: I need to onboard a new ERP customer company in BankIntegration, Add a user who can administer a company's bank agreements, Refresh a company's registration details from the CVR register, Create a bank agreement for a customer so payments can flow

Not supported: Does not move funds, reconcile transactions, or handle accounting or tax filing; use it to administer BankIntegration customers, users, agreements, and accounts only.

The BankIntegration ERP API lets accounting and ERP software vendors administer their own customers inside the Danish BankIntegration platform. It creates and updates companies, users, bank agreements, and accounts, and refreshes company records from the Danish CVR business register. Canonical reference lists cover banks, bank centrals, countries, and currencies so an integration can validate payment routing before it opens an agreement.

Jentic One on Github View OpenAPI Document

Connect the BankIntegration Erp API to your agent

Capabilities

Start building with BankIntegration Erp API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Api2 Bankintegration Dk BankIntegration Erp API