Install Jentic One Beta

Connect the NBG Account and Transaction API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NBG Account and Transaction 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%2Fnbg.gr%2Faccount-and-transaction-uk" | 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%2Fnbg.gr%2Faccount-and-transaction-uk" | 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 NBG Account and Transaction API.

Create, read, and delete account-access consents

List a customer's accounts and read account details and balances

Retrieve account transactions over a date range

Read standing orders, scheduled payments, and beneficiaries for an account

Fetch account statements and their transactions or files

GET STARTED

Start building with NBG Account and Transaction API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NBG Account and Transaction API for, with concrete tasks.

★ Account and Balance Aggregation

An AI agent aggregates a customer's NBG accounts and balances after they authorize access. Following the UK Open Banking flow, the agent creates an account-access consent, then lists accounts and reads balances, so a finance assistant can present an up-to-date position without screen scraping.

Create an account-access consent, then call list accounts and read balances once the customer has authorized access.

Transaction Retrieval for Reconciliation

A workflow pulls a customer's transactions to reconcile against internal records. The account transactions operation returns entries over a date range for an authorized account, giving an agent the data it needs to match and categorize spending.

Read the account transactions for an authorized account over the required date range and reconcile them.

Consent Lifecycle Management

An agent sets up and monitors the access consents that UK Open Banking requires. The consent operations create a new account-access consent, read its status, and delete it when access is no longer needed, letting an agent manage access cleanly.

Create an account-access consent, check its status, and delete it once access is finished.

Key Endpoints

21 endpoints — the nbg account and transaction api gives authorized third parties read access to a customer's account information at the national bank of greece, following the uk open banking v3.

METHOD

PATH

DESCRIPTION

POST

/account-access-consents

Create an account-access consent

GET

/accounts

List authorized accounts

GET

/accounts/{accountId}/balances

Read an account's balances

GET

/accounts/{accountId}/transactions

Read an account's transactions

GET

/accounts/{accountId}/statements

List an account's statements

POST

/account-access-consents

Create an account-access consent

GET

/accounts

List authorized accounts

GET

/accounts/{accountId}/balances

Read an account's balances

GET

/accounts/{accountId}/transactions

Read an account's transactions

GET

/accounts/{accountId}/statements

List an account's statements

Why Jentic?

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

Setup

Wiring the NBG Account and Transaction API by hand means following the UK Open Banking flow yourself: create a consent with the OAuth2 client credentials token, send the customer through authorization, then read account data with the OAuth2 authorization code token and the Client-Id header. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Because operations are addressed by consent, account, and statement IDs, a rule can pin your agent to reading balances on one account without touching consents. You choose the operations and resources it may reach, so the rest stay out of scope unless you add them.

Credential isolation

Your NBG Client-Id and OAuth2 tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'read open banking transactions' or 'list bank accounts', and Jentic returns the matching NBG operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NBG Account and Transaction API through Jentic.

What authentication does the NBG Account and Transaction API use?

Every request sends the application's Client-Id header, an apikey credential, plus an OAuth2 token, per its OpenAPI spec and the UK Open Banking v3.1.5 profile. Setting up an account-access consent uses the OAuth2 client credentials flow, while reading account data uses the OAuth2 authorization code flow after the customer authorizes access. Through Jentic these credentials are stored encrypted in your own Jentic One instance and injected at call time.

How does account access work in the NBG Account and Transaction API?

It follows the UK Open Banking model: you create an account-access consent, the customer authorizes it, and then your agent reads accounts, balances, transactions, and statements within that consent. The consent operations let an agent set up and check access before requesting any data.

What are the rate limits for the NBG Account and Transaction API?

The OpenAPI spec does not specify rate limits. Because it follows the UK Open Banking v3.1.5 profile, check the NBG developer portal for the applicable limits before scheduling regular account reads.

How do I read account transactions with the NBG Account and Transaction API through Jentic?

Search Jentic for 'read open banking transactions', add the NBG Account and Transaction API from the directory, and your agent creates a consent, then reads the account transactions once the customer has authorized access, using your stored Client-Id and OAuth2 token. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an NBG Account and Transaction API MCP server?

You don't need an MCP server to give your agent the NBG Account and Transaction API. Jentic connects it directly from the API Directory: import it, store your Client-Id and OAuth2 credentials once, and your agent calls the consent and account operations. Nothing extra loads into the agent's context until a call is made.

Can I limit what my agent is allowed to do with the NBG Account and Transaction API?

Yes. Write a rule that allows just the operations you want, such as reading balances and transactions without creating consents, so the agent cannot call anything else, and every call is logged. Because operations are scoped by consent, account, and statement IDs, rules can bound the exact accounts your agent reaches.

Nbg Gr NBG Account and Transaction API

Name: NBG Account and Transaction API
Brand: NBG Account and Transaction API
Availability: InStock

Community OpenAPI document · agent-readyFinanceBankingoauth221 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create UK Open Banking account-access consents and read a customer's accounts, balances, transactions, standing orders, and statements at the National Bank of Greece once access is authorized.

Use for: Set up account access consent for a customer, List the accounts I have consent to read, Get recent transactions for this account, Show the balance on this account

Not supported: Does not handle payment initiation, card issuing, or lending. Use for reading UK Open Banking account and transaction information only.

The NBG Account and Transaction API gives authorized third parties read access to a customer's account information at the National Bank of Greece, following the UK Open Banking v3.1.5 account and transaction profile. It creates and manages account-access consents, then reads accounts, balances, transactions, beneficiaries, standing orders, scheduled payments, and statements once the customer has authorized access.

Jentic One on Github View OpenAPI Document