African APIs,
ready for AI agents.
A machine-readable registry of African API specs — payments, SMS, identity, logistics and beyond. One plugin. Every provider. Any AI agent.
Run an African API? Get it listed
One command.
Every African API.
Install the afrotools plugin and your AI agent instantly knows how to integrate any provider in the registry. No copy-pasting docs. No trial and error.
Skills activate automatically on install.
Which agent do you use?
/ plugin marketplace add afrotools/ afrotools
/ plugin install afrotoolsMCP server only: claude mcp add --transport http afrotools https:/
Run inside Claude Code. The plugin adds the MCP server plus the payment, sms and debug skills.
Try it: ask your agent "Integrate Paycard payment in my Next.js app"
How it works
From spec to working integration in minutes, not days.
- 01
Structured specs
Every African API is described in a machine-readable JSON schema — endpoints, auth, input & response shapes, and the gotchas the docs leave out.
- 02
Your AI agent reads the spec
Through the afrotools plugin or MCP server, your agent pulls the exact spec for the capability it needs — like the Flutterwave charge shown here.
- 03
Your app works
The agent writes the integration code. You review, ship, and move on. No more deciphering incomplete docs.
- endpoint
- POST https:/
/ f4bexperience. flutterwave. com/ charges - auth
- oauth2 · FLUTTERWAVE_CLIENT_CREDENTIALS
- currency
- GHS KES NGN RWF SLE TZS UGX XAF XOF ZAR ZMW
- sandbox
- yes
gotchas · 11
- Successful creation returns HTTP 201, not 200. Treat both as success when reading response.ok.
- X-Trace-Id is REQUIRED on this endpoint (12-255 chars). Omitting it will return a 400 validation error — generate a fresh UUID per request and forward it through any retries.
Featured providers
13 providers · 150 capabilities · 26 countries — ready to integrate today.
Run an African API?
Get it listed.
Your API, described so every AI agent integrates it correctly. Share your docs — a link or a PDF is enough — and we write the open-source ATSS spec. Prefer to do it yourself? Open a pull request.
How a capability moves through the registry
- Available141 capabilities
- Spec written and validated — endpoints, auth, schemas and at least one gotcha. Agents can integrate it right away.
- Verified9 capabilities
- A working example exists in afrotools/examples and a maintainer has checked it.
- Gotchas stay public
- Providers can't pay to edit or remove them. That honesty is why developers trust the specs.