apipay is now apifare — same product, same tokens. New home: apifare.com. This address keeps working for 90 days.
apifare × LibreChat
Give every user of your LibreChat instance their own prepaid tool balance: no separate provider account or provider API key for eligible capabilities — one apifare account gives their agent a capped, auditable budget. One YAML block; no LibreChat code changes; off unless the user connects.
The config (works today)
LibreChat's customUserVars prompts each user for their own token and stores
it encrypted. Add this to librechat.yaml:
mcpServers:
apifare:
type: streamable-http
url: https://apipay.fly.dev/mcp
headers:
Authorization: "Bearer {{APIPAY_TOKEN}}"
customUserVars:
APIPAY_TOKEN:
title: "apifare token"
description: "Prepaid tool balance - get one at https://apipay.fly.dev (shown once at signup)."
Local/desktop installs can use stdio instead:
command: npx, args: ["-y", "apifare-mcp"],
env: {APIPAY_TOKEN: "{{APIPAY_TOKEN}}"}.
APIPAY_TOKEN is the env name (legacy install id).
What your users see
Each user pastes their token once on the connection screen:
When their balance runs out mid-task, the paywall shows up inside the chat — a human-readable line with the top-up link and the spend cap; after topping up, the task resumes. Failed provider calls are refunded.
What's callable
The current catalog with exact per-call prices is at /capabilities — the listed number is what the balance is debited (one source of truth, CI-enforced). Spend guardrails live wallet-side: per-agent caps, kill switch, signed audit export.
For operators
You never touch the money — each user funds their own balance. Sign-ups made from your
instance can carry "origin":"app:librechat" so we both see the integration
working. Questions or a listing/doc conversation:
github.com/iamalanlui/apipay.