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.
register_free_key. The server returns a key with 25 credits, with no signup, email or card.api_key and deducts credits: 1 for an email check, 1 for a token scan, 3 for a full website audit.Servers: VerifAI · SiteDoctor · RugShield
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.
| Credits on a key | x402 | |
|---|---|---|
| Agent needs a wallet | No | Yes (USDC) |
| Human in the loop | Only to top up | No |
| Works in Claude, Cursor or VS Code today | Yes, as a plain remote MCP server | Needs an x402-capable client |
| Price granularity | From $0.00099 per credit | From $0.0001 per call |
Machine-readable index: /.well-known/mcp.json · /llms-full.txt · /openapi.json (credit checkout)