Jumo
JUMO is a Cape Town-based banking-as-a-service (BaaS) platform, founded in 2015, that uses artificial intelligence to power digital credit and savings products for banks, mobile network operators, and payments providers across emerging markets in Africa. Its infrastructure has two foundational capabilities: Core, an end-to-end next-generation banking platform that replaces legacy core banking with no build cost, and Unify, an AI processor that transforms alternative data (such as GSM records and mobile wallet transactions) to reduce the cost and risk of lending. JUMO delivers financial services through partners including Airtel, MTN Group, Orange Money Group, and Mukuru, and has disbursed over USD 8 billion to more than 31 million people across Ghana, Kenya, Tanzania, Zambia, Uganda, Cote d'Ivoire, South Africa, Benin, and Cameroon. It is a certified B Corporation backed by investors including Anthemis, LeapFrog Investments, Fidelity Management, and Visa. JUMO's APIs and integrations are provided privately to regulated financial-institution partners rather than through a public developer portal.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Jumo the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Jumo scores 15.2/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Jumo
Each block below is one kind of artifact we hold for Jumo. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Jumo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/jumo · machine-readable index on apis.io