Afro.tools — AI-ready infrastructure for African APIs

Integrate Wave, Paycard, and any African API in a single prompt.

African APIs are production-grade. What's been missing is a standard,
machine-readable format that AI agents can consume directly — without
parsing documentation pages or guessing at request shapes.

Afro.tools fills that gap: a static, open-source registry of structured
specs for African APIs, written from each provider's official documentation.
Every provider is AI Ready: an agent gets a structured description of
exactly what it needs to generate integration code. A spec can still contain
errors — its status says how far it has been checked (verified = tested
against the provider's API by a maintainer).

How it works

graph LR
    A["specs/ — open source"] -->|GitHub raw URLs| B["MCP server\nmcp.afro.tools"]
    B -->|MCP protocol| C["AI agent\nClaude · Cursor · Copilot · ..."]
    C -->|generates| D["Integration code\nin your app"]
    A -->|plugin| C

What is a spec?

A spec lives at specs/{category}/{provider}/{capability}/ and contains exactly two files:

• schema.json — ATSS-compliant description of the API capability (endpoint, auth, input/output schemas, gotchas)
• canonical_example.ts — TypeScript implementation using native fetch, compiles with tsc --noEmit

Each provider also has a provider.json at the root of its folder:

specs/payment/paycard/
├── provider.json                    ← metadata + description + example_prompt
├── create_payment/
│   ├── schema.json
│   └── canonical_example.ts
├── verify_payment/
└── webhook_payment_completed/

See ATSS.md for the full specification.

Providers

Legend: ✅ All verified = all capabilities verified · X verified · Y ready = Y specs not yet tested against the API · 📋 Ready = written from the docs, not yet tested · 🗓 Planned = specs coming soon

Use with an MCP client

Claude Code

claude mcp add --transport http afrotools https://mcp.afro.tools/mcp

Cursor / Windsurf / VS Code Copilot

{
  "mcpServers": {
    "afrotools": {
      "type": "http",
      "url": "https://mcp.afro.tools/mcp"
    }
  }
}

Claude Code plugin

/plugin install afrotools --marketplace afrotools/afrotools

On Claude Code older than 2.1.275, in two steps:

/plugin marketplace add afrotools/afrotools
/plugin install afrotools

Auto-activated skills based on context:

• payment — integrating a payment API
• communications — integrating an SMS, WhatsApp, USSD, voice or email API
• identity — integrating an identity verification (KYC, document, AML) API
• logistics — integrating a delivery or courier API (price, book, track, cancel deliveries)
• language — integrating a speech-to-text or text-to-speech API for African languages
• debug — when an integration based on an afrotools spec fails → diagnoses whether the problem is a spec error, a missing gotcha, or an undocumented API change

Manual commands:

• /afrotools:spec <provider> <capability> — inspect a full spec
• /afrotools:list — list all available specs
• /afrotools:new <category> <provider> <capability> — scaffold a new spec
• /afrotools:studio — afro.tools Studio: from an idea to an app in production for African markets (a short plan, a clean design, mobile money, SMS and WhatsApp wired from the registry, checks before going live). Works for non-developers too: it explains in plain words and asks only what it must
• /afrotools:check — before going live: keys in the code or the browser, payments confirmed server-side, nothing paid twice, webhooks verified
• /afrotools:review [audit] — a code review or security audit by a separate reviewer
• /afrotools:diagnose — something went wrong with Studio or a skill: a cleaned bug report you submit yourself

Studio offers three optional companions once, never required: superpowers (planning method), Impeccable (designs the screens and critiques them before any code) and Playwright MCP (checking screens in a browser).

Contributing

See CONTRIBUTING.md to add a spec or improve an existing one.

Integrated a provider? Report it — worked or not, sandbox or
production. A report that worked can make the spec verified, credited to you; one that did not
gets the spec fixed.

Spec lifecycle: draft → ready → verified

Every provider in the registry is AI Ready: its specs give an agent a structured, machine-readable description to integrate it. AI Ready is not a guarantee that a spec is error-free — verified marks the specs tested against the provider's API — by a maintainer or through an accepted integration report — and says where: sandbox or production.

License

Apache 2.0 — see LICENSE.