Mkhisa7 Account API

Name: Account API
Brand: Account API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingnone4 Endpoints

Install Jentic One Beta

Connect the Account API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account 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://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 API.

Get Balance

Account Enquiry

Integrate Account API into automated workflows

Query and filter Account API records by parameters

GET STARTED

Start building with Account API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Account API for, with concrete tasks.

★ Payments Operations

Use the Account API to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including get balance, get full account statement, get mini statement.

Call GET /accounts/balances/{countryCode}/{accountNumber} to get balance

Automated accounts Management

Automate accounts operations by combining multiple Account API endpoints. Agents can get full account statement and then get mini statement in a single workflow.

Call POST /accounts/fullstatement to get full account statement, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Account API 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 none tokens manually.

Search Jentic for 'get balance', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — the equity bank account api allows a merchant to fetch full/minimal transaction details for a given operative account, do account enquiries and get a list of accounts opened.

METHOD

PATH

DESCRIPTION

GET

/accounts/balances/{countryCode}/{accountNumber}

Get Balance

POST

/accounts/fullstatement

Get Full Account Statement

GET

/accounts/ministatement/{countryCode}/{accountNumber}

Get Mini Statement

GET

/search/{countryCode}/{accountNumber}

Account Enquiry

GET

/accounts/balances/{countryCode}/{accountNumber}

Get Balance

POST

/accounts/fullstatement

Get Full Account Statement

GET

/accounts/ministatement/{countryCode}/{accountNumber}

Get Mini Statement

GET

/search/{countryCode}/{accountNumber}

Account Enquiry

Why Jentic?

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

Credential isolation

Any access details for the Account API 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 'get an account balance' or 'fetch a mini statement', and Jentic returns the matching Account API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Account API through Jentic.

What authentication does the Account API use?

The Account API uses no authentication. 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 balance with the Account API?

Yes. Use the GET /accounts/balances/{countryCode}/{accountNumber} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Account API?

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 balance through Jentic?

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

How many endpoints does the Account API have?

The Account API exposes 4 endpoints covering accounts, search operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which of the four operations your agent may call and which stored credentials it may use. Because the country code and account number sit in the URL path, such as GET /accounts/balances/{countryCode}/{accountNumber}, you can pin the agent to reading the balance and mini statement for a single account. Broader operations like POST /accounts/fullstatement or the account enquiry search stay off limits unless you explicitly add them.

Mkhisa7 Account API

Connect the Account API to your agent

Capabilities

Start building with Account API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs