canonical: https://jentic.com/apis/swaggerhub.openpayments/account-information-service

# Openpayments Account Information Service

Open Banking Platform PSD2 API - Account Information Summary The **NextGenPSD2** *Framework Version 1.3.3* offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and,. The API exposes 5 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically read account list, read account details. Covers 5 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Read Account List
- Manage finance data programmatically
- Integrate Account Information Service into automated workflows
- Query and filter Account Information Service records by parameters
- Monitor Account Information Service operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Account Information Service (AIS)** — The Account Information Service (AIS) offers the following services
  * Transaction reports for a gi

## Why Jentic

- **Setup:** Wiring the Account Information Service by hand means running its OAuth2 flow, tracking token refresh, and calling its open-banking sandbox host yourself. Through Jentic you install once, import Account Information Service from the API Directory, store the OAuth2 credentials once, and your agent calls it.
- **Permission scoping:** Account Information Service puts the account id in the URL path (/v1/accounts/{account-id}/balances and /transactions), so a rule can pin your agent to one account. You choose the operations it may call, so it can stay on reading balances and transactions for that account and nothing else unless you add it.
- **Credential handling:** Your Account Information Service OAuth2 credentials 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.
- **Discovery method:** Agents search Jentic by intent such as 'read the account list' or 'get an account's transactions', and Jentic returns the matching Account Information Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Account Information Service?

Yes. Because you run Jentic One yourself, your own rules decide which Account Information Service operations and credentials the agent may use. Since the account id sits in the URL path for endpoints like GET /v1/accounts/{account-id}/balances and /v1/accounts/{account-id}/transactions, you can pin the agent to a single account and allow only the read operations you approve. It can stay on reading balances and transactions for that account and call nothing else unless you grant it.