Install Jentic One Beta

Connect the Akoya API to your agent

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

Retrieve a customer's accounts held at a data provider

Read current and available balances for those accounts

Pull transaction history for a specific account

Fetch statements and individual statement documents

Look up payment network details for an account

GET STARTED

Start building with Akoya API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Akoya API for, with concrete tasks.

★ Consumer-Permissioned Account Aggregation

An AI agent can retrieve a customer's accounts at a data provider and read their balances, giving a consented financial snapshot without screen scraping. Because Akoya standardizes data across institutions, the same logic works regardless of the underlying bank. Through Jentic the agent discovers the accounts operation by intent and runs it with credentials injected at call time.

List the customer's accounts at their provider and return the balances

Transaction Retrieval

A financial agent can pull an account's transaction history for a period and feed it into categorization, reconciliation, or reporting. The standardized shape means the agent parses one format across providers. It reads only the account it is scoped to.

Pull the transactions for account 55512345 from the last statement period

Statement Access

An agent can list an account's statements and fetch a specific statement document for review or archival. This lets it gather statements on a schedule without a person downloading each one. The agent accesses only statements for the permissioned account.

Fetch the most recent statement for this account and summarize it

Key Endpoints

9 endpoints — the akoya api provides consumer-permissioned access to financial account data through data providers.

METHOD

PATH

DESCRIPTION

GET

/accounts/{version}/{providerId}

List a customer's accounts at a provider

GET

/balances/{version}/{providerId}

Get account balances

GET

/transactions/{version}/{providerId}/{accountId}

Get transactions for an account

GET

/accounts-info/{version}/{providerId}

Get detailed account information

GET

/customers/{version}/{providerId}/current

Get the current customer profile

GET

/statements/{version}/{providerId}/{accountId}

List statements for an account

GET

/accounts/{version}/{providerId}

List a customer's accounts at a provider

GET

/balances/{version}/{providerId}

Get account balances

GET

/transactions/{version}/{providerId}/{accountId}

Get transactions for an account

GET

/accounts-info/{version}/{providerId}

Get detailed account information

GET

/customers/{version}/{providerId}/current

Get the current customer profile

GET

/statements/{version}/{providerId}/{accountId}

List statements for an account

Why Jentic?

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

Setup

Wiring the Akoya API by hand means handling its HTTP Basic and bearer authentication, tracking provider and account IDs across its operations, and parsing the standardized data formats yourself. Through Jentic you install once, import Akoya from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Akoya addresses accounts and transactions by provider and account ID in the URL path, so you can scope the agent to a single provider or account. Because every operation is read-only, an agent can be limited to reading balances without access to statements or payment details.

Credential isolation

Your Akoya 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 'retrieve bank account balances' or 'pull transaction history', and Jentic returns the matching Akoya operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Akoya API through Jentic.

Is there an Akoya MCP server?

You don't need an MCP server to connect your agent to the Akoya API. Jentic imports it from the API Directory, stores your credentials once, and your agent reads accounts and transactions directly. No extra server sits in the agent's context.

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

Yes. Because accounts and transactions are addressed by provider and account ID in the URL path, you can scope the agent to a single provider or account and, since every operation is read-only, allow just the data it needs. It can read balances without touching statements or payment details. Every call is logged.

What authentication does the Akoya API use?

The Akoya API uses HTTP Basic authentication as declared in its OpenAPI spec, alongside a bearer token for data access. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected when the agent makes a call, so they never appear in the agent's prompt or logs.

Can my agent read transaction history with the Akoya API?

Yes. The transactions operation returns an account's activity for a period, so an agent can build spending views or feed reconciliation without direct bank scraping.

Can the Akoya API move money or change account data?

No. The Akoya operations in this spec are read-only data retrieval for accounts, balances, transactions, statements, and payment networks, so an agent using it can read financial data but cannot initiate transfers or edit accounts.

How does my agent pull account data with the Akoya API through Jentic?

Search Jentic for 'retrieve bank account balances' and it returns the Akoya accounts operation with its input schema. Store your credentials once, then the agent supplies the provider and reads back the accounts and balances. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Akoya API

Name: Akoya API
Brand: Akoya API
Availability: InStock

Community OpenAPI document · agent-readyFinanceBankingbasic9 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Retrieve consumer-permissioned financial data through Akoya: a customer's accounts, balances, transactions, statements, payment networks, and profile details, all as read-only lookups.

Use for: List the accounts this customer holds at their bank, Get the current balance for this account, Pull the transaction history for this account, Fetch the latest statement for this account

Not supported: Does not initiate payments, open accounts, or provide credit scoring. Use for consumer-permissioned financial data retrieval only.

The Akoya API provides consumer-permissioned access to financial account data through data providers. It retrieves a customer's accounts, balances, transactions, statements, payment networks, and account and contact details, giving applications a standardized way to read financial data across the institutions Akoya connects.

Jentic One on Github View OpenAPI Document