Pay-per-call MCP tools: how agents pay for tools without subscriptions

Most MCP servers are either free or tied to a SaaS account. Pay-per-call is a third model. The agent gets a key from the server itself, spends credits per call, and someone tops it up when it runs low. Here is how it works on our three MCP servers and on the x402 API.

Model 1: credits on a self-minted key (MCP)

  1. The agent calls register_free_key. The server returns a key with 25 credits, with no signup, email or card.
  2. Every paid tool takes api_key and deducts credits: 1 for an email check, 1 for a token scan, 3 for a full website audit.
  3. When credits run out, the tool returns an error with payment instructions.
  4. A human buys a pack by card ($9 / $29 / $99), pasting the key to top it up or leaving it empty to get a new key. Credits are added automatically after payment.

Servers: VerifAI · SiteDoctor · RugShield

Model 2: pay per request with x402 (HTTP)

The server answers 402 Payment Required with a price, and the agent pays in USDC and retries. There are no keys at all. See Wallet Doctor.

Which to choose

Credits on a keyx402
Agent needs a walletNoYes (USDC)
Human in the loopOnly to top upNo
Works in Claude, Cursor or VS Code todayYes, as a plain remote MCP serverNeeds an x402-capable client
Price granularityFrom $0.00099 per creditFrom $0.0001 per call

Try it

Machine-readable index: /.well-known/mcp.json · /llms-full.txt · /openapi.json (credit checkout)