Mono
Mono is an open banking and financial data infrastructure company for Africa (often described as the "Plaid for Africa"), headquartered in Lagos, Nigeria and now part of Flutterwave. Its REST APIs let businesses link customer bank accounts and retrieve financial data (accounts, transactions, identity, income, balance, statements, assets, earnings), assess creditworthiness, collect direct bank payments via DirectPay (direct debit), and verify identity data (BVN, NIN, CAC, account numbers) through the Lookup services. Server-to-server calls authenticate with a secret key sent in the `mono-sec-key` header, and account linking is completed through the hosted Mono Connect widget.
Mono publishes 6 APIs on the APIs.io network, including Connect API, Creditworthiness API, DirectPay API, and 3 more. Tagged areas include Open Banking, Financial Data, Payments, Fintech, and Account Linking.
Mono’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Mono Connect API
Account linking authorization and re-authorization.
Mono Creditworthiness API
Affordability and credit-decisioning analysis.
Mono DirectPay API
Direct bank payment collection.
Mono Financial Data API
Read financial data from a linked account.
Mono Investment API
Investment holdings for a linked account.
Mono Lookup API
Identity and data verification for KYC/KYB.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Mono API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Mono Africa Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Mono Africa Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API