AbaPay

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "AbaPay": {
      "url": "https://agents.abapays.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (11)

• describe_capabilities read-only

  List what AbaPay can pay (airtime, data, electricity, cable, etc.), any services currently paused, and example requests. Call this first if unsure what is supported.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_balance read-only

  Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once this connector is authorized via OAuth.

  Parameters:

  • chain — string — Defaults to the chain approved when the key was created.
  • api_key — string — AbaPay MCP API key (starts with aba_mcp_). NOT needed when the connector is authorized via OAuth — omit it entirely in that case; only supply it if this server asked you to authenticate and OAuth is unavailable.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_plans read-only

  List the REAL, currently purchasable plans for a service that needs one — DATA bundles, CABLE packages, or EDUCATION products (WAEC/JAMB) — with their exact codes and current VTpass prices. ALWAYS call this before pay_bill for these three services and pass back one of the returned codes as variation_code. Never guess a plan, a code, or a price — if this returns nothing usable, say so rather than inventing one.

  Parameters:

  • service (required) — string — Which service to list plans for. Electricity and airtime are free-amount and have no plan list.
  • provider (required) — string — e.g. mtn, airtel, glo, 9mobile (data); dstv, gotv, startimes (cable); waec, waec-registration, jamb (education)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_international_options read-only

  Browse the REAL, live international top-up catalogue (140+ countries) one level at a time. Call with no country to see supported countries. Add country to see its product types. Add product_type_id to see operators. Add operator_id too to see real, currently purchasable plans with their exact codes, foreign-currency price, and NGN-equivalent cost. ALWAYS call this before pay_bill with service: INTERNATIONAL, and pass back the exact country/product_type_id/operator_id/variation_code shown — never guess any of them. Only plans marked fixed-price can be paid via pay_bill right now; flexible-amount plans must be completed in the AbaPay app.

  Parameters:

  • country — string — Country name or ISO code, e.g. "Ghana" or "GH". Omit to list all supported countries.
  • operator_id — string — An operator_id returned for this country + product_type_id — the network to top up. Omit to list operators.
  • product_type_id — string — A product_type_id returned for this country — e.g. which kind of top-up (airtime vs a data bundle). Omit to list the country's product types.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• transaction_history read-only

  List recent real transactions for the linked wallet — same data as the AbaPay app's History tab (service, provider, amount, status, tx hash). Read-only, no PIN required. The interactive card's own Next/Previous buttons page through results by re-calling this tool with a different offset — pass offset yourself only when asked for something like "the next page" or "transactions before that" in plain text.

  Parameters:

  • limit — number — How many recent transactions to return. Defaults to 10, max 25.
  • offset — number — How many of the most recent transactions to skip before listing — 0 (default) starts at the newest. Used for paging: offset=10 with the default limit gets the next 10 after the first page.
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_payment_status read-only

  Look up one payment by its reference — the transaction hash (0x…) or the request id a payment returned — and get its current status in plain words: delivered, still being confirmed, failed, or refunded, including where any refund stands. Only finds payments made by the linked wallet. Read-only, no PIN required. Use this instead of paying again when a pay_bill result was lost.

  Parameters:

  • reference (required) — string — The transaction hash (0x…) or request id of the payment.
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• pay_bill destructive

  Pay a real bill — Nigerian (airtime, data, electricity, cable TV, a WAEC/JAMB education PIN) or international airtime/data across 140+ countries — from the linked wallet, settled on-chain and delivered via the same pipeline as the AbaPay app. For DATA, CABLE (when changing package), and EDUCATION, call list_plans first and use a real variation_code from it. For service: INTERNATIONAL, call list_international_options first and pass back its exact country/product_type_id/operator_id/variation_code — never guess any of these. ALWAYS requires the PIN — including when this connector is authorized via OAuth; ask the human for it every time and never guess or reuse a remembered one. Money moves for real — only call this once the human has clearly confirmed the exact amount, provider, and account. EXECUTES IMMEDIATELY, with no delay/schedule parameter of any kind — there is no way to queue this call for later on this connection. If the human asks to pay "in N minutes", "later today", "tomorrow", or any other future time, do NOT call this now: ask them to confirm they want it sent immediately instead, or tell them delayed/recurring automations can only be set up from the AbaPay app or by messaging the AbaPay agent on Telegram/WhatsApp/X — never silently pay right away when a delay was requested.

  Parameters:

  • pin (required) — string — The PIN set when the API key was created (6 digits for new keys). Required on EVERY payment, including over an OAuth connection — ask the human for it each time.
  • service (required) — string — Which kind of bill
  • account_number (required) — string — Phone number (airtime/data), meter number (electricity), smartcard/IUC number (cable), JAMB profile ID (education: jamb), the buyer's phone number (education: waec), or the destination phone number abroad (international)
  • chain — string — Defaults to the chain approved when the API key was created. Only override this if the default chain lacks balance/allowance and check_balance shows funds on the other one.
  • token — string — Which stablecoin to pay with. Defaults to the token approved when the API key was created. If that one is short on balance or on-chain allowance, call check_balance first to see what else is available on this chain, then retry with this field set — e.g. if USD₮ is short but the wallet holds USDC with its own approved limit, pass token: "USDC".
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
  • country — string — Required for service: INTERNATIONAL — country name or ISO code, from list_international_options.
  • provider — string — e.g. mtn, airtel, glo, ikeja-electric, dstv, gotv, startimes, waec, waec-registration, jamb. Not used for service: INTERNATIONAL — use country/product_type_id/operator_id instead.
  • amount_ngn — number — Amount in Naira. Not needed for service: INTERNATIONAL — the NGN-equivalent is derived from the live plan you picked via list_international_options.
  • meter_type — string — Required for ELECTRICITY
  • operator_id — string — Required for service: INTERNATIONAL — from list_international_options.
  • customer_name — string — Optional — used for the receipt if known
  • customer_email — string — Required for service: INTERNATIONAL (the receipt goes here). Optional otherwise.
  • variation_code — string — Plan/bundle/product code — required for DATA, EDUCATION, and INTERNATIONAL, and for CABLE when changing package (not needed to renew the current one)
  • idempotency_key — string — Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with different arguments is refused (409). Without one, an identical call within 2 minutes is treated as a retry.
  • product_type_id — string — Required for service: INTERNATIONAL — from list_international_options.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• schedule_bill

  Set up a recurring or future one-off bill payment — daily/weekly/monthly airtime, data, electricity, or cable — the same automation Telegram/WhatsApp/X support. Validates exactly like pay_bill (call list_plans first for DATA, or CABLE when changing package, to get a real variation_code) and ALWAYS requires the PIN, since this creates a standing spend. Nothing is charged when this tool runs — money only moves later, when the schedule actually fires, and only if the wallet still has a funded on-chain allowance at that time. If the approved agent limit already covers the amount right now, the schedule is created to auto-pay itself each time it is due; otherwise it is saved as notify-only and someone must call pay_bill manually when it comes due — the response says which. EDUCATION and INTERNATIONAL cannot be scheduled; pay those directly with pay_bill. Use list_schedules to see what is set up and cancel_schedule to remove one.

  Parameters:

  • pin (required) — string — The PIN set when the API key was created (6 digits for new keys). Required to create a schedule, same as pay_bill.
  • service (required) — string — Which kind of bill to schedule. EDUCATION and INTERNATIONAL are not schedulable — use pay_bill directly for those.
  • account_number (required) — string — Phone number (airtime/data), meter number (electricity), or smartcard/IUC number (cable)
  • amount_ngn (required) — number — Amount in Naira to charge each time the schedule runs.
  • frequency (required) — string — How often this runs. "once" fires exactly one time, schedule_in_minutes from now.
  • chain — string — Defaults to the chain approved when the API key was created.
  • token — string — Defaults to the token approved when the API key was created.
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
  • provider — string — e.g. mtn, airtel, glo, 9mobile, ikeja-electric, dstv, gotv, startimes
  • meter_type — string — Required for ELECTRICITY
  • day_of_week — number — Required when frequency is "weekly" — 0 (Sunday) through 6 (Saturday).
  • day_of_month — number — Required when frequency is "monthly" — 1 through 28.
  • customer_email — string — Where to send a notification when this runs. MCP has no persistent channel to message back into a conversation — without this, you'll need to poll list_schedules or transaction_history yourself to see what happened.
  • variation_code — string — Plan/bundle/product code — required for DATA, and for CABLE when changing package (not needed to renew the current one). Get a real one from list_plans first.
  • idempotency_key — string — Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with different arguments is refused (409). Without one, an identical call within 2 minutes is treated as a retry.
  • schedule_in_minutes — number — Required when frequency is "once" — minutes from now to run it a single time.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• list_schedules read-only

  List active recurring/one-off bill schedules for the linked wallet — same data as the AbaPay app and Telegram/WhatsApp "show my schedules". Read-only, no PIN required. Returns each schedule's id — pass that to cancel_schedule to remove one.

  Parameters:

  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• cancel_schedule destructive

  Cancel active schedules for the linked wallet. Call list_schedules first to get a real id. Pass id to cancel exactly one (no PIN needed). Cancelling several at once — provider for every schedule of that provider, or all: true for every schedule on this wallet — requires the PIN, asked from the human each time. Calling with none of id/provider/all is refused rather than cancelling everything.

  Parameters:

  • id — string — The exact schedule id from list_schedules. Cancels only that one schedule. No PIN needed.
  • all — boolean — Set true to cancel EVERY active schedule on this wallet. Requires pin. Never inferred — must be passed explicitly.
  • pin — string — The PIN set when the API key was created. Required with provider or all; not needed for a single id.
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
  • provider — string — Cancel every active schedule for this provider, e.g. "mtn". Requires pin. Ignored if id is also given.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• pay_bill_batch destructive

  Pay airtime or data to multiple recipients in ONE call — the same multi-recipient batch Telegram/WhatsApp/X support ("send 500 to X and 1000 to Y"). One PIN authorizes the whole batch. Recipients are grouped by (chain, token); each group's capacity (balance + approved agent limit) is checked against that group's own subtotal — but if ANY group is short, the ENTIRE batch is refused before anything moves (all-or-nothing on capacity; paying 6 of 8 recipients because the 7th was under-funded is worse than one clear error up front). Once capacity clears, recipients are paid one at a time and the response reports each individually, since a single vend failure partway through must not be reported as if the whole batch failed. AIRTIME and DATA only — electricity, cable, education, and international are not batchable; call pay_bill for those, one at a time. For DATA, call list_plans first and give each recipient needing one its own real variation_code. EXECUTES IMMEDIATELY: no delay/schedule option, same as pay_bill — for a delayed/recurring batch, call schedule_bill once per recipient instead.

  Parameters:

  • pin (required) — string — The PIN set when the API key was created (6 digits for new keys). Required once for the whole batch.
  • recipients (required) — array — At least 2 recipients (a single recipient should just use pay_bill), at most 20 per call — split a larger batch across several calls.
  • chain — string — Default chain for recipients that don't set their own. Falls back to the chain approved when the API key was created.
  • token — string — Default token for recipients that don't set their own. Falls back to the token approved when the API key was created.
  • api_key — string — AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
  • customer_email — string — Optional — used for receipts if known, applies to the whole batch.
  • idempotency_key — string — Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with different arguments is refused (409). Without one, an identical call within 2 minutes is treated as a retry.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.