Install Jentic One Beta

Connect the ASPSP Information Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ASPSP 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.openpayments%2Faspsp-information-service" | 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%2Fswaggerhub.openpayments%2Faspsp-information-service" | 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 ASPSP Information Service API.

Get ASPSPs

Manage payments data programmatically

Integrate ASPSP Information Service into automated workflows

Query and filter ASPSP Information Service records by parameters

Monitor ASPSP Information Service operational status and events

GET STARTED

Start building with ASPSP Information Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Payments Operations

Use the ASPSP Information Service to perform payments operations programmatically. The API provides 6 endpoints covering core functionality including get aspsps, get aspsp, get cities.

Call GET /v1/aspsps to get aspsps

Automated ASPSP Information Service (ASPSPIS) Management

Automate aspsp information service (aspspis) operations by combining multiple ASPSP Information Service endpoints. Agents can get aspsp and then get cities in a single workflow.

Call GET /v1/aspsps/{bicFi} to get aspsp, then verify the result

AI Agent Integration via Jentic

AI agents discover and call ASPSP 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 'get aspsps', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — open payments platform psd2 core api - aspsp information.

METHOD

PATH

DESCRIPTION

GET

/v1/aspsps

Get ASPSPs

GET

/v1/aspsps/{bicFi}

Get ASPSP

GET

/v1/cities

Get cities

GET

/v1/cities/{city-id}

Get city

GET

/v1/countries

Get countries

GET

/v1/countries/{isoCountryCode}

Get countries

GET

/v1/aspsps

Get ASPSPs

GET

/v1/aspsps/{bicFi}

Get ASPSP

GET

/v1/cities

Get cities

GET

/v1/cities/{city-id}

Get city

GET

/v1/countries

Get countries

GET

/v1/countries/{isoCountryCode}

Get countries

Why Jentic?

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

Setup

Wiring the ASPSP 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 ASPSP Information Service from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

ASPSP Information Service puts the reference id in the URL path (/v1/aspsps/{bicFi}, /v1/cities/{city-id}, /v1/countries/{isoCountryCode}), so a rule can pin your agent to one ASPSP lookup. You choose the operations it may call, so it can stay on reading ASPSP, city, and country references and nothing else unless you add it.

Credential isolation

Your ASPSP 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.

Intent-based discovery

Agents search Jentic by intent such as 'list ASPSPs' or 'look up an ASPSP by BIC', and Jentic returns the matching ASPSP Information Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ASPSP Information Service API through Jentic.

What authentication does the ASPSP Information Service use?

The ASPSP 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 get aspsps with the ASPSP Information Service?

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

What are the rate limits for the ASPSP 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 get aspsps through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get aspsps'. Jentic returns the matching ASPSP Information Service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the ASPSP Information Service have?

The ASPSP Information Service exposes 6 endpoints covering aspsp information service (aspspis) operations.

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

Yes. Jentic One is self-hosted, so you write the rules that decide which ASPSP Information Service operations your agent may call and which stored credentials it may use. Because the service puts the reference id in the URL path (/v1/aspsps/{bicFi}, /v1/cities/{city-id}, /v1/countries/{isoCountryCode}), you can pin the agent to a single ASPSP, city, or country lookup. You can also keep it on read-only reference calls like GET /v1/aspsps and GET /v1/countries and add nothing else unless you choose to.

Openpayments ASPSP Information Service

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

Browse all Swaggerhub Openpayments APIs

Community OpenAPI document · agent-readyPaymentsPayment Processingoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically get aspsps, get aspsp. Covers 6 operations with oauth2 authentication.

Use for: I need to aspsps, I want to aspsp, Search for cities, Find all city

Not supported: Does not handle communications, crm, or developer tools - use for payments only.

Open Payments Platform PSD2 Core API - ASPSP Information. The API exposes 6 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Connect the ASPSP Information Service to your agent

Capabilities

Start building with ASPSP Information Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Openpayments ASPSP Information Service