Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mono 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%2Fmono.co%2Fmono" | shStep 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%2Fmono.co%2Fmono" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Mono API.
Initiate account linking and exchange the authorization token
Read linked account balances, transactions, identity, and statements
Assess account creditworthiness and retrieve income data
Initiate one-time payments and verify or refund them
Create and manage direct debit mandates and debit against them
GET STARTED
Run BVN, bank, and account-number lookups across supported countries
Patterns agents use Mono API for, with concrete tasks.
★ AI agent open banking access via Jentic
An AI agent connected through Jentic reads a linked account without wiring Mono's auth flow by hand. It searches by intent such as reading account transactions, Jentic returns the matching Mono operation with its input schema, and the agent fetches balances, transactions, and identity for a linked account. The developer's own Jentic One instance injects the API key at call time.
Call GET /v2/accounts/{id}/balance for a linked account, then GET /v2/accounts/{id}/transactions to read its history
Account linking and financial data
Fintech apps onboard a customer's bank account to read their finances. Mono initiates account linking, exchanges the authorization token, then returns account details, identity, income, and statements, so an agent can complete the link and pull a financial picture for underwriting or budgeting.
Call POST /v2/accounts/initiate to start linking, then POST /v2/accounts/auth to exchange the token
Payments and refunds
Merchants collect and reverse one-time payments. Mono initiates a payment, verifies its status by reference, lists payment transactions, and refunds a payment, so an agent can take a bank payment and reconcile or reverse it, with figures handled in the lowest denomination of the currency.
Call POST /v2/payments/initiate to start a payment, then GET /v2/payments/verify/{reference} to confirm it
Direct debit mandates
Lenders and subscription businesses collect recurring debits. Mono creates a direct debit mandate, lists and retrieves mandates, cancels one, and debits an account against an active mandate, so an agent can set up recurring collection and trigger a debit when a payment is due.
Call POST /v3/payments/mandates to create a mandate, then POST /v3/payments/mandates/{id}/debit when a payment is due
33 endpoints — the mono api is an open banking platform for africa that links customer bank accounts and reads their financial data.
METHOD
PATH
DESCRIPTION
/v2/accounts/initiate
Initiate account linking
/v2/accounts/{id}/balance
Get account balance
/v2/accounts/{id}/transactions
Get account transactions
/v2/accounts/{id}/creditworthiness
Assess creditworthiness
/v2/payments/initiate
Initiate a one-time payment
/v2/payments/verify/{reference}
Verify payment status
/v3/payments/mandates
Create a direct debit mandate
/v3/lookup/account-number
Account number lookup
/v2/accounts/initiate
Initiate account linking
/v2/accounts/{id}/balance
Get account balance
/v2/accounts/{id}/transactions
Get account transactions
/v2/accounts/{id}/creditworthiness
Assess creditworthiness
/v2/payments/initiate
Initiate a one-time payment
/v2/payments/verify/{reference}
Verify payment status
/v3/payments/mandates
Create a direct debit mandate
/v3/lookup/account-number
Account number lookup
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mono API by hand means learning its mono-sec-key header, completing the account linking and token exchange, and tracking that figures arrive in the lowest denomination of each currency. Through Jentic you install once, import Mono from the API Directory, store the key once, and your agent calls the account and payment operations.
Permission scoping
Mono puts the account id in the URL path (/v2/accounts/{id}/transactions), so a rule can pin your agent to one linked account and the read operations on it. You choose the operations it may call, so initiating payments, refunding, or debiting a mandate are not included unless you add them.
Credential isolation
Your Mono secret key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read account transactions' or 'initiate a payment', and Jentic returns the matching Mono operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Mono API through Jentic.
What authentication does the Mono API use?
The Mono API authenticates with an API key sent in the mono-sec-key header, per its OpenAPI spec. Through Jentic, your secret key is stored encrypted by your own Jentic One instance and injected into the mono-sec-key header at execution time, so it never enters the agent's prompt or logs.
Can I read a linked account's transactions with the Mono API?
Yes. After linking is complete, the account operations return balances, transactions, identity, income, and statements for a linked account id. Figures are reported in the lowest denomination of the account currency, such as kobo for Nigerian naira.
What are the rate limits for the Mono API?
The OpenAPI spec does not state numeric rate limits. Check the Mono documentation at https://docs.mono.co for current limits across the account, payment, and lookup operations.
How do I link a bank account through Jentic?
Search Jentic by intent such as linking an account, and it returns the Mono account-initiate operation with its input schema. Start linking, exchange the authorization token, then read the account data, with your key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Mono API?
Yes. Mono puts the account id in the URL path, such as /v2/accounts/{id}/transactions, so a rule can pin your agent to the read operations on one linked account so it fetches balances and transactions and nothing else. State-changing operations such as initiating a payment or debiting a mandate stay out unless you add them, and every call is logged by your self-hosted instance.
Is there a Mono API MCP server?
You do not need an MCP server to give your agent the Mono API. Jentic connects it directly from the API Directory: import it, store your secret key once, and your agent calls the account and payment operations on demand without loading another server's tool definitions into its context.
For Agents
Link African bank accounts and read balances, transactions, identity, and statements, initiate payments and direct debit mandates, and run BVN and account-number lookups.
Use for: I need to link a customer's bank account, I want to read the transactions on a linked account, Get the balance for a linked account, Initiate a one-time payment
Not supported: Does not issue cards, hold balances, or handle tax filing. Use for bank account linking, financial data, payments, and direct debit only.
The Mono API is an open banking platform for Africa that links customer bank accounts and reads their financial data. It initiates account linking, exchanges the authorization token, and then returns account details, balances, transactions, identity, income, and statements. It assesses creditworthiness, initiates one-time payments and refunds, manages direct debit mandates, and runs BVN, bank, and account-number lookups across Nigeria, Ghana, Kenya, and South Africa. Response figures are in the lowest denomination of each currency.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>