Openpayments Account Information Service

Name: Account Information Service API
Brand: Account Information Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth25 Endpoints

Install Jentic One Beta

Connect the Account Information Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account Information Service, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Account Information Service API.

Read Account List

Manage finance data programmatically

Integrate Account Information Service into automated workflows

Query and filter Account Information Service records by parameters

GET STARTED

Start building with Account Information Service API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Account Information Service API for, with concrete tasks.

★ Finance and Accounting Operations

Use the Account Information Service to perform finance operations programmatically. The API provides 5 endpoints covering core functionality including read account list, read account details, read balance.

Call GET /v1/accounts to read account list

Automated Account Information Service (AIS) Management

Automate account information service (ais) operations by combining multiple Account Information Service endpoints. Agents can read account details and then read balance in a single workflow.

Call GET /v1/accounts/{account-id} to read account details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Account Information Service endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Search Jentic for 'read account list', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — open banking platform psd2 api - account information summary the **nextgenpsd2** *framework version 1.

METHOD

PATH

DESCRIPTION

GET

/v1/accounts

Read Account List

GET

/v1/accounts/{account-id}

Read Account Details

GET

/v1/accounts/{account-id}/balances

Read Balance

GET

/v1/accounts/{account-id}/transactions

Read transaction list of an account

GET

/v1/accounts/{account-id}/transactions/{transactionId}

Read Transaction Details

GET

/v1/accounts

Read Account List

GET

/v1/accounts/{account-id}

Read Account Details

GET

/v1/accounts/{account-id}/balances

Read Balance

GET

/v1/accounts/{account-id}/transactions

Read transaction list of an account

GET

/v1/accounts/{account-id}/transactions/{transactionId}

Read Transaction Details

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Account Information Service oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'read account list') and Jentic returns the matching Account Information Service operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Account Information Service integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Account Information Service API through Jentic.

What authentication does the Account Information Service use?

The Account Information Service uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I read account list with the Account Information Service?

Yes. Use the GET /v1/accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Account Information Service?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I read account list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'read account list'. Jentic returns the matching Account Information Service operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Account Information Service have?

The Account Information Service exposes 5 endpoints covering account information service (ais) operations.

Openpayments Account Information Service

Connect the Account Information Service to your agent

Capabilities

Start building with Account Information Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs