Okra
Okra was an open finance / open banking infrastructure company for Africa, headquartered in Lagos, Nigeria. Its REST APIs let businesses link end users' bank accounts (via the Okra Widget and a per-record "record" object) and then retrieve authenticated banking data - account and identity details, real-time balances, transaction history, and income - plus run KYC verifications (BVN, NUBAN, TIN, RC) and move money through bank-to-bank payments and direct debit authorizations. RETIRED: Okra quietly ceased operations in May 2025 and wound the company down; the API hosts (api.okra.ng, dash.okra.ng, docs.okra.ng, identity-api.okra.ng) no longer resolve and the okra.ng domain now serves an unrelated parked page. This entry documents the historical, now-discontinued API surface, grounded in Okra's official okraHQ/okra-node SDK and archived documentation.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Okra the way a machine reads it — 19 machine-readable artifacts across 12 APIs, 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 — Okra scores 38.6/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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.
How we profile Okra
Each block below is one kind of artifact we hold for Okra. 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.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Okra Accounts API
Bank accounts a customer has linked.
Okra Auth API
Authentication data for linked bank accounts.
Okra Balance API
Real-time and cached account balances.
Okra Banks API
Reference list of connectable banks.
Okra Customers API
End-user (customer) management.
Okra Identity API
Verified identity profiles.
Okra Income API
Income and affordability signals.
Okra Payments API
Bank-to-bank payments and direct-debit authorizations.
Okra Reports API
Scheduled financial reports.
Okra Transactions API
Categorized transaction history.
Okra Verification API
Nigerian KYC checks (BVN, NUBAN, TIN, RC).
Okra Wallet API
Billing wallet used to fund API usage.
Scroll within the panel for all 12 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Okra API (Historical)
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Okra Africa Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Okra Africa Finops
FINOPSSecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Okra — 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.
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/okra-africa · machine-readable index on apis.io