MTN Group publishes 119 APIs on the network. Africa’s largest mobile network operator, headquartered in Johannesburg, roughly 290 million subscribers across around 16 markets, and the operator of MoMo — one of the continent’s largest mobile-money platforms.
It scores 50.1, a developing band. Its agent readiness is 51.1, band agent-native.
An African carrier is more agent-ready than Microsoft Graph, Mastercard and Siemens. That deserves an explanation.
The developer surface is genuinely open
Unusually for a carrier, MTN publishes without a gate. The MTN Developer Platform (MADAPI) at developers.mtn.com lists 221 API products across 15 African markets, and lets anyone download the OpenAPI or Swagger definition for a product without an account. Separately, momodeveloper.mtn.com is a self-serve portal with a working sandbox for the MoMo Collection, Disbursements and Remittance APIs.
Downloading a carrier’s contract without registering is rare. Testing a carrier’s payment rails in a sandbox without a commercial agreement is rarer.
TM Forum is why the contracts hold up
MTN’s catalog is heavily shaped by TM Forum Open APIs — TMF620, TMF621, TMF622, TMF629, TMF632, TMF633, TMF635, TMF637, TMF639, TMF652, TMF654, TMF658, TMF666, TMF667, TMF676, TMF677, TMF678, TMF681, TMF683, TMF685, TMF688 and TMF720.
The catalog holds 115 contracts at 89.6% callable, and standardisation is why. When your product catalog, customer bill management and resource inventory APIs follow a published industry specification, the shape is decided before anyone writes it. MTN South Africa is also a GSMA Open Gateway participant, which puts CAMARA network APIs alongside the TM Forum BSS surface.
Standards adoption is the cheapest route to contract quality available to a carrier, and MTN took it.
The facets say where the work is
| Facet | Score |
|---|---|
| Discoverability | 68.5 |
| Contract quality | 63.2 |
| Developer ergonomics | 62.5 |
| Commercial clarity | 34.2 |
| Operational transparency | 21.1 |
| Governance | 20.8 |
Governance at 20.8 and operational transparency at 21.1 are the lowest pair in this week’s seven profiles. There is no meaningful published governance layer — no rulesets, no versioning policy, no deprecation practice visible in the artifacts — and almost no operational signalling.
MTN also carries the Telecommunications regulatory regime, scoring 66.7 — the highest regulatory-layer score of the week, well above Webex’s 58.3 and Mastercard’s 36.7.
Agent-native, honestly earned
475 operations, 246 acting, 14 human-in-the-loop.
Fourteen consent markers against 246 acting operations is roughly one in eighteen — second only to Webex’s ratio this week, and on a surface that moves money in markets where mobile money is the banking system.
The agent-native band comes from the combination the rest of the catalog keeps failing: downloadable contracts without registration, a live sandbox, standardised operation shapes, and 89.6% callability. An agent can discover, read, test and call this surface without a human intermediary at any step.
Takeaway
119 APIs, 89.6% callable, TM Forum throughout, a public sandbox for mobile money, and an agent-native readiness band — sitting on top of a 20.8 governance score. MTN got discovery and access right and has not yet published the governance layer. That is the opposite of the usual enterprise failure, and the easier half to fix second.
See the full profile at apis.io/providers/mtn-group/.