Apipay

io.github.iamalanluiPublished by GitHub account iamalanluiv0.4.2Updated Oct 24, 2026

Prepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts.

Overview

AI-generated overview

Apipay (apifare) lets an assistant search and call a catalog of ready-made APIs, paying per call from a prepaid credit balance.

What you can do
Search the apifare catalog of ready-to-call APIs and see each API's slug, parameters and per-call price in credits, with misses logged for later addition to the catalog. Call a catalog API by slug, with the credit cost deducted automatically and returned with the result. Get a one-time vault link so the user can store their own provider API key (BYOK) instead of pasting it into chat. Check the prepaid credit balance and get a top-up link, or trigger a top-up under the owner's standing auto-refill mandate. Call vendor management APIs (Supabase, Vercel, Fly, Resend, GitHub, npm, Cloudflare, Lemon Squeezy) with the owner's vaulted root credential injected server-side. Move or generate secrets,
When to use it
Useful when an assistant needs to run web search, scraping, weather or other ready-made API calls without wiring up each provider, and when it should manage vendor accounts or move secrets without exposing values in the conversation.
Requirements
Runs as a remote endpoint or as a local npm package (apifare-mcp, stdio). Requires an APIPAY_TOKEN bearer token obtained from the apifare signup endpoint, and a prepaid credit balance for paid calls. Network access to apifare and the called vendors is needed.
Before you install
Calls spend prepaid credits (1 credit = $0.01), and top-up can charge the owner's payment mandate within configured limits. The APIPAY_TOKEN is a secret. Vendor calls act with the owner's vaulted root credentials and can change vendor resources; destructive, billing and member/admin routes are stated to be blocked. Secret transfer and generation place real secrets at vendors server-side.

Installation

In SourceWeft

  1. Open Apipay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.iamalanlui%2Fapipay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apipay": {
      "type": "http",
      "url": "https://apifare.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

8

search_apis

Search the API catalog

Search the apifare catalog of ready-to-call APIs (web search, scraping, weather, and more). Returns each API's slug, params, and per-call price in prepaid credits. Every miss is logged so missing APIs get added.

Parametersqueryrequired

call_api

Call an API (spends prepaid credits)

Call an API from the apifare catalog by slug (find slugs with search_apis). The cost in prepaid credits is deducted automatically and returned with the result.

Parametersslugrequiredparams

check_balance

Check the prepaid balance

Check the remaining apifare prepaid credit balance (1 credit = $0.01) and get the top-up link.

Takes no parameters.

topup

Top up the balance (charges the owner's card)

Top up the apifare balance from the owner's standing auto-refill mandate (if the owner enabled one). Charges within the owner's configured limits and returns the new balance. Without a mandate, returns payment instructions to relay to the user.

Parametersamount_usd

vendor_call

Call a vendor management API

Call a vendor MANAGEMENT API (supabase, vercel, fly, resend, github, npm, cloudflare, lemonsqueezy) with the owner's vaulted root credential injected server-side. Native request/response; destructive, billing, and member/admin routes are blocked. The root token is never visible.

Parametersbodypathrequiredmethodvendorrequired

secret_transfer

Move a secret between vendors, server-side

Move a secret from one vendor to another SERVER-SIDE — the value never enters this conversation. Example: fetch a Supabase service_role key and place it as a Vercel env var.

Parameterstorequiredfromrequired

secret_generate

Generate a secret and place it at a vendor

Generate a random secret and place it directly at a vendor resource SERVER-SIDE — the value never enters this conversation.

Parameterstorequiredbytes

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.