Install Jentic One Beta

Connect the finAPI Access API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the finAPI Access 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%2Ffinapi.io%2Ffinapi" | 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%2Ffinapi.io%2Ffinapi" | 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 finAPI Access API.

Issue an OAuth 2.0 access token via POST /oauth/token using client credentials

Provision an end user under your finAPI client and link them to bank connections

Create a new bank connection by initiating the PSD2 SCA flow on POST /bankConnections

List the bank connections owned by a given finAPI user

Delete a bank connection when an end user revokes consent

GET STARTED

Start building with finAPI Access API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use finAPI Access API for, with concrete tasks.

★ Embedded Open Banking Onboarding

Fintechs that need to read SMB transaction data can have an agent provision the end user via POST /users, then call POST /bankConnections to start the PSD2 strong customer authentication flow. Once consent is granted, the agent stores the connection id and downstream services can read account data through the same finAPI session.

Call POST /users to create the user, then POST /bankConnections with the bank id and SCA configuration, and store the connection id with the user record.

Consent Revocation Handling

Compliance teams operating under PSD2 need to honour consent revocations promptly. An agent can listen for revoke events from the host application and call DELETE /bankConnections/{id} on the finAPI side to ensure the bank connection is removed and no further data calls succeed against the revoked link.

On revoke event, look up the user's connection ids, then DELETE /bankConnections/{id} for each, then mark the host record as revoked.

Service-To-Service Token Refresh

Backend automations that hit finAPI on a schedule can have an agent refresh the OAuth client credentials token by calling POST /oauth/token before the previous token expires, then cache the new bearer for subsequent calls. This keeps the polling loop running without 401-driven retries.

On token expiry, call POST /oauth/token with the client credentials grant and replace the cached bearer used by the polling worker.

AI Agent finAPI Integration via Jentic

An agent connected to Jentic can search by intent (for example provision a finapi user) and Jentic returns the matching finAPI operation along with its input schema. The OAuth client credentials and per-user bearer tokens live in your Jentic One instance, which is critical given finAPI's BaFin-licensed status. Integration drops from a multi-week PSD2 onboarding to under an hour.

Search Jentic for create a finapi bank connection, load POST /bankConnections, and execute with the user id and bank id while Jentic injects the bearer token from the vault.

Key Endpoints

15 endpoints — the finapi access api is a bafin-licensed open banking interface that gives applications access to bank account data, payment initiation, and aggregated banking information across european institutions.

METHOD

PATH

DESCRIPTION

POST

/oauth/token

Issue an OAuth access token

POST

/users

Provision a new end user

GET

/users

List end users under your client

DELETE

/users/{userId}

Delete an end user

GET

/bankConnections

List bank connections

POST

/bankConnections

Create a new bank connection

GET

/bankConnections/{id}

Retrieve a bank connection

DELETE

/bankConnections/{id}

Delete a bank connection

POST

/oauth/token

Issue an OAuth access token

POST

/users

Provision a new end user

GET

/users

List end users under your client

DELETE

/users/{userId}

Delete an end user

GET

/bankConnections

List bank connections

POST

/bankConnections

Create a new bank connection

GET

/bankConnections/{id}

Retrieve a bank connection

DELETE

/bankConnections/{id}

Delete a bank connection

Why Jentic?

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

Setup

Wiring the finAPI Access API by hand means running the OAuth2 client-credentials flow at /oauth/token, choosing between the sandbox and live hosts, and managing per-user bearer tokens for PSD2 provisioning yourself. Through Jentic you install once, import the finAPI Access API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

finAPI puts the user id and bank-connection id in the URL path (/users/{userId}, /bankConnections/{id}), so a rule can pin your agent to the users and connections you allow. You choose the operations it may call, so a destructive action like deleting a user or a bank connection is not included unless you add it.

Credential isolation

Your finAPI client credentials and per-user bearer tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. The OAuth client secret never enters the agent's prompt, logs, or context, which matters for a BaFin-licensed integration.

Intent-based discovery

Agents search Jentic by intent such as 'link a bank account' or 'provision a new user', and Jentic returns the matching finAPI operation with its input schema, so the agent does not have to walk the full PSD2 spec.

FAQs

Specific to using finAPI Access API through Jentic.

What authentication does the finAPI Access API use?

finAPI uses OAuth 2.0 client credentials for service tokens via POST /oauth/token, plus bearer tokens for per-user calls. Through Jentic, both the client credentials and user tokens live in the encrypted vault and are injected at execution.

Can I link a bank account with the finAPI Access API?

Yes. Provision the user via POST /users, then call POST /bankConnections to begin the PSD2 SCA flow against the chosen bank. Once the end user completes SCA, the connection becomes usable for downstream account information calls.

What are the rate limits for the finAPI Access API?

finAPI applies per-client throttling and the spec does not publish a fixed RPS. Sandbox traffic is limited more aggressively than production. Agents should respect 429 responses with exponential backoff and avoid bursting on /bankConnections during SCA flows.

How do I revoke a bank connection through Jentic?

Search Jentic for revoke a finapi bank connection, load the DELETE /bankConnections/{id} operation, and execute with the connection id. Jentic injects the bearer token from the vault and finAPI removes the connection on the bank side.

Is the finAPI Access API free to use?

finAPI offers a sandbox at sandbox.finapi.io for development, but production use against live.finapi.io requires a commercial agreement and a BaFin-licensed contract because the underlying service is regulated.

Can I list all bank connections for a user with finAPI?

Yes. Call GET /bankConnections with the user context to enumerate that user's links. Agents can then iterate the connections to refresh transaction data or surface revocation candidates.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which finAPI operations and credentials the agent may use. Because finAPI puts the user id and bank-connection id in the URL path (/users/{userId}, /bankConnections/{id}), you can pin the agent to the specific users and connections you allow. You also choose the operations it may call, so a destructive action like DELETE /users/{userId} or DELETE /bankConnections/{id} is excluded unless you add it.

finAPI Access API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingbearer, oauth215 EndpointsREST

For Agents

Provision end users and bank connections under a BaFin-licensed open banking platform via OAuth 2.0 and bearer tokens.

Use for: Issue a finAPI OAuth access token for service-to-service calls, Provision a new finAPI end user, Create a bank connection for a finAPI user, List bank connections for a finAPI user

Not supported: Does not handle card acquiring, KYC/identity verification, or accounting bookkeeping - use for PSD2 user provisioning and bank connection management only.

The finAPI Access API is a BaFin-licensed open banking interface that gives applications access to bank account data, payment initiation, and aggregated banking information across European institutions. It exposes 15 endpoints covering OAuth client-credentials token issuance, end-user provisioning, and bank-connection management. Authentication is by OAuth 2.0 client credentials for service-to-service calls and bearer tokens for end-user-scoped operations. The API is used by fintechs and embedded-finance products that need PSD2-compliant access to retail and SMB bank accounts in the DACH region and beyond.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

72%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the finAPI Access API to your agent

Capabilities

Start building with finAPI Access API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

finAPI Access API

Jentic AI Readiness Score

finAPI Access API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness