27 July 2026 · Wycord
The State of African Digital Infrastructure 2026
The first annual report generated from Wycord's own registry: 381 verified resources, spanning 9 categories of African digital infrastructure, measured. What exists, what is open, what is gated, and where the gaps are.
Every number in this report comes from one source: the Wycord registry, where each entry has had its documentation opened, its licensing confirmed and its live status verified. This is not a survey or an estimate. It is a census of the African digital infrastructure that builders can actually use, as of July 2026.
The headline numbers
The registry holds 381 verified resources across 9 categories, spanning more than 20 African countries and pan-African providers.
| Category | Verified resources |
|---|---|
| APIs | 105 |
| Developer tools | 60 |
| MCP servers | 54 |
| Datasets | 52 |
| AI resources | 48 |
| SDKs | 20 |
| Research | 17 |
| Open source | 16 |
| AI agents | 9 |
Three findings stand out.
1. The infrastructure mostly works. 367 of 381 resources (96 percent) have live, reachable documentation as of the latest automated verification pass. Only one resource in the registry is confirmed dead (shut down outright); the rest of the non-live entries are broken, unreachable or redirected docs rather than dead projects. The African infrastructure story is not one of broken links; it is one of fragmented discovery.
2. About a quarter of it is gated. 92 resources (24 percent) require approval, institutional access or payment before a developer can use them. Identity and KYC infrastructure is the most gated domain, a direct consequence of data-protection regulation such as Nigeria's NDPC regime. Builders should budget for licensing lead time, not just integration time.
3. The AI-agent layer is growing fastest, and unevenly. MCP servers grew from 42 to 54 in the past three weeks alone, now the second-largest category in the registry and the largest labelled collection of African-infrastructure MCP servers anywhere. Deployable AI agents, by contrast, held flat at 9, the smallest category. The rails to let AI agents call African infrastructure are being built quickly; the autonomous layer running on top of them is still just starting.
Where the infrastructure lives
| Coverage | Resources |
|---|---|
| Nigeria | 190 |
| Pan-African | 72 |
| Kenya | 41 |
| South Africa | 20 |
| Ethiopia | 10 |
| Ghana | 7 |
| Egypt | 6 |
| Rwanda | 5 |
| Senegal | 5 |
| Benin | 4 |
Nigeria remains the deepest market by a wide margin, with 190 verified resources, nearly double the combined total of Kenya, South Africa, Ethiopia, Ghana, Egypt, Rwanda, Senegal and Benin (98 resources together). The most notable movement in 2026 is outside the big four: Ethiopia's payment infrastructure (Chapa, ArifPay), francophone West Africa's rails (Wave, FedaPay, CinetPay, PayDunya, KkiaPay) and Rwanda's voice-AI work now all have verified, documented entry points.
Open data, measured
Of 52 verified African datasets, 49 are usable without approval or payment. Geographic and boundary data, population estimates and African-language NLP corpora are the strongest openly available domains. The hardest data to obtain remains exactly where builders need it most: property, granular telecom statistics and post-2006 census data. The full breakdown is maintained live in the African Open Data Index.
The connection layer
Infrastructure does not exist alone. The registry maps operating companies to their products and records typed relationships between resources: which SDK serves which API, which MCP server wraps which provider. These connections are browsable on every resource page and in the relationship graph. The graph is still young and growing with every verification pass, as more of the registry's cross-references get mapped explicitly rather than left implicit.
What is still missing
The registry also tracks what should exist and does not. The most consequential gaps, unchanged through 2026: no official result-verification APIs for JAMB, WAEC or NECO; no CBWu o fficual FX REST API; no NAFDAC drug-verification API; no property title or ownership verification anywhere on the continent's largest markets. Each of these is a business waiting for a builder, and several are harder regulatory problems than techincal ones.
Method
Wycord verifies rather than aggregates. Every resource's documentation is opened by a human or an automated check before listing; docs status is re-verified by an automated pass every few days, and every status transition is recorded publicly in the changes feed. Counts in this report are generated from the registry API and reproducible by anyone: the entire dataset is open at wycord.com/api/resources.
This is the first anual edition. The registry is a living census, and next year's report will measure not just what exists, but what changed.