# io.github.iamalanlui/apipay

- Registry name: `io.github.iamalanlui/apipay` · version 0.4.2
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Payments & accounting, Finance & markets, Databases
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.iamalanlui%2Fapipay
- Server page: https://mcpstation.net/s/io.github.iamalanlui--apipay.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://apifare.com/mcp`

## Tools (as reported by the server, not verified)

- `search\_apis`: 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.
- `call\_api`: 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.
- `get\_vault\_link`: Get a secure one-time link where the user can save their OWN API key for a provider \(BYOK\). Never ask the user to paste an API key into the chat — always use this link instead. BYOK calls cost a flat 0.1 credits; the user's own provider account pays the provider.
- `check\_balance`: Check the remaining apifare prepaid credit balance \(1 credit = $0.01\) and get the top-up link.
- `topup`: 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.
- `vendor\_call`: 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.
- `secret\_transfer`: 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.
- `secret\_generate`: Generate a random secret and place it directly at a vendor resource SERVER-SIDE — the value never enters this conversation.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html