# Pay for many tools and APIs from one prefunded balance

> Pay for many tools and APIs from one prefunded balance: 1 companies fully do it, 6 with a limit, 23 carry the tag. Every listing in Payment & monetisation platforms with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/payment-platforms.pay-from-balance/
- Markdown: https://www.anchorterminal.com/niches/payment-platforms.pay-from-balance/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/payment-platforms.pay-from-balance/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/payment-platforms.pay-from-balance/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 6 | 23 | 12 | 3 |

## What counts as done

The agent pays several services from one balance under a cap the person set, each charge is recorded with service, amount and time, and a failed charge is reported so the agent does not retry blindly, with the steps that need a person listed in the docs.

How agents ask for it: use my credits to pay for search and images; give the agent a balance for paid tools; top up the agent account

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Nevermined API + MCP (Nevermined AG)**: A Delegation a person approves carries a hard cap in cents, an expiry and optional recipient list, checked server-side on every payment; requestId stops a retry paying twice (409 with the original paymentId), list_payments records each payment, and setup_delegation returns the URL the person must open.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **ATXP (Circuit & Chisel, Inc.)**: One prefunded account pays the LLM gateway, hosted tools and paid MCP servers, and agents can self-register with 5 USD credit. The client's default approvePayment returns true for every payment, no service-side cap was found, and the terms bar automated agents creating accounts.
- **Circle Gateway Nanopayments (Circle Technology Services, LLC)**: One Gateway balance pays many x402 sellers gas-free, but the cap is the deposit itself or a client-side hook; no service-side spending cap a person sets was found.
- **Crossmint API + Docs MCP (Crossmint, Inc.)**: A card-funded Agent Wallet pays x402 and MPP endpoints, and a signer scope sets a per-token spending limit with a reset interval, a recipient list and an expiry, checked before broadcast. Scopes cover only the transfer type, so whether x402's signed authorisations count against them is not stated.
- **FluxA AgentMarket (FluxA Technology Pte. Ltd.)**: One prepaid Balance pays listed APIs and models, and the ledger lists each spend with id, time, change, remaining balance and model. Per-key spendLimit covers metered usage only, and an agent holding an Agent VC can raise or clear it itself.
- **Skyfire API + MCP (Skyfire Systems Inc.)**: A buyer wallet funded by card or Base USDC pays any Skyfire seller, and each pay token commits a maximum the seller cannot exceed. Caps are per token set by the agent, not a person-set budget across services, and only Skyfire sellers are reachable.
- **Tempo (Tempo Labs Inc.)**: A Tempo Wallet access key carries a daily spending limit and expiry the person approves and can lower, Tempo enforces it on every transaction, and keys are revoked at wallet.tempo.xyz/apps. Per-charge records with the service named and failed-charge reporting were not shown in the pages read.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Payman Genie MCP (Payman AI, Inc.)**: Owner-set limits and approvals are said to live in the Genie account, which the bridge forwards to without deciding anything, but the developer docs that would state caps, history and x402 support could not be opened.

- not this job: Adyen MCP server (Adyen N.V.): Merchant-side server; no buyer balance or paying of other services.
- not this job: Lago (Get Lago Corp.): Lago wallets are prepaid credits a seller sells for its own product, not a buyer balance that pays other services.
- not this job: Metronome (Stripe, LLC): Credits and commits are a seller's prepaid balances for its own product, not a buyer balance across services.
- not this job: Orb (Orb, Inc.): Prepaid credits are a seller's customers' balances for its own product, not a buyer balance across services.
- not this job: Paid (Agent Paid Limited): Credits and credit caps are a seller's customers' balances for its own product, not a buyer balance across services.
- not this job: PayPal MCP server (PayPal, Inc.): Merchant tools only; no buyer balance or paying other services.
- not this job: Stripe API + MCP (Stripe, LLC): Stripe here is the seller side. Shared payment tokens are issued from the separate Onelink Agent Wallet; the API and MCP offer no buyer balance that pays several services under a cap.
- not this job: TermiX AACP (TermiX): Each order is funded into escrow from the acting wallet; no shared balance with a person-set cap.

## What stops agents finishing

- 3D Secure on off-session card payments
- default client approves every payment
- terms that bar automated agents from creating accounts

## Around it

Before: agent-wallets.fund-and-cap. After: agent-observability.cost-report.

## Where this comes from

Weight 12 of 100 in Payment & monetisation platforms: 3 of 23 accounts (acc-21, acc-22, acc-23), none on a listed balance product (ATXP, FluxA AgentMarket, Nevermined Router, Payman)

As data: https://www.anchorterminal.com/api/v1/use-cases/payment-platforms.pay-from-balance.json, or the MCP tool get_use_case with id payment-platforms.pay-from-balance. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
