How to monetize an MCP server: per-call payments with x402

ScriptMasterLabs monetizes MCP servers with per-call x402 billing on Base: the server answers unpaid tool calls with a 402 challenge, the agent pays in USDC, and a facilitator settles on-chain. SML’s machine-readable x402 manifest lists network eip155:8453, USDC, and agent id 74033 on the ERC-8004 registry, verified live September 22, 2026.

The way to monetize an MCP server without subscriptions, API keys, or accounts is per-call x402 billing: your server answers each unpaid tool call with a 402 Payment Required challenge carrying price, asset, network, and payTo address; the agent's wallet signs the payment authorization, retries the same call, and a facilitator settles it on-chain. ScriptMasterLabs runs this model live on Base today — the receipts below are a working machine-readable payment manifest and a live MCP server handshake you can inspect yourself, not screenshots.

Honesty note. SML's marketplace paid reads are currently quarantined (status PARTIAL_REOPEN_PROVIDER_LISTING_ONLY, verified live September 22, 2026) — the live billable line is the one-time 0.01 USDC provider listing fee on Base. SML publishes no revenue figures, and this page claims none. What we can prove is the infrastructure: the manifest, the headers, the handshake.

What do the current top answers get wrong?

The current top answers get this wrong: AgenticMarket’s vendor pitch takes a 10–20% platform cut with no live payment proof; Stripe payment links use $19/mo and $99/mo subscriptions shaped for human checkout, not agent-native billing; and xpay.sh’s proxy page markets a “95% revenue share” with no auditable code and a calculator that multiplies assumptions, not transactions.

How do you put the meter on your server as a seller?

To put the meter on your server as a seller, know what a 402 challenge must carry, challenge inside your tool handler, consider a zero-code proxy wrapper, price from the live market, and get discovered where agents look.

1. Know what a 402 challenge must carry. Price, asset, network, payTo, expiry, and resource binding — terms the buyer can verify before signing. Receiving a challenge always costs the caller nothing.
2. Challenge inside your tool handler. On tools/call without a payment credential, return the payment terms: as JSON-RPC error data on the MCP transport, or as 402 with a PAYMENT-REQUIRED header/body on HTTP. Verify the buyer's signature through a facilitator (live example from our manifest: https://api.cdp.coinbase.com/platform/v2/x402), settle on-chain, run the tool, return the result with a PAYMENT-RESPONSE receipt.
3. Zero-code alternative: a proxy wrapper. Services like xpay.sh or ag402 paste in front of your server: you set per-tool prices, agents get a monetized proxy URL, you change zero code. The tradeoff is real: the proxy holds your upstream credentials, takes a cut, and you cannot audit what you cannot see. For production tools, own the challenge handler.
4. Price from the live market. SML's provider listing is a one-time 0.01 USDC on Base (verified live tonight). ProBlocks runs a live x402 demo endpoint at 0.001 USDC per call on Base (September 2026). Price per call by cost (compute), usage (tokens, bytes, seconds), or outcome — the protocol sets no price, each seller does.
5. Get discovered where agents look. Coinbase's Bazaar catalogue; the SML Provider Marketplace (one-time 0.01 USDC x402 listing; discovery is free).

How do agents or scripts pay for tools?

Agents or scripts pay for tools by inspecting terms free, verifying before signing, and keeping the PAYMENT-RESPONSE receipt — settlement proves value moved on-chain, not that the tool returned correct data.

1. Inspect terms free. curl https://squeezeos-api.onrender.com/.well-known/x402 — the manifest costs nothing to read, and neither does receiving a 402 challenge.
2. Verify before you sign. Price, asset, network, recipient, expiry, resource binding. Cap amounts; restrict destinations.
3. Keep the PAYMENT-RESPONSE receipt. Settlement proves value moved on-chain — it does not prove the tool returned correct, complete data. Verify delivery separately.

Where does ScriptMasterLabs fit?

ScriptMasterLabs fits through the SML Provider Marketplace (one-time 0.01 USDC provider listing on Base), the live mcp-x402 server with x402 billing, the x402 Protocol Guide PDF field guide ($29), and the machine-readable x402 manifest.

• SML Provider Marketplace — the live x402 v2 listing contract: one-time 0.01 USDC provider listing on Base; discovery free.
• mcp-x402 — SML's live MCP server with x402 billing infrastructure (dual-rail x402: EIP-3009 facilitator plus sovereign viem; listed on RelAI.fi and APIHub.io). Live handshake verified above.
• x402 Protocol Guide (PDF, $29) — the full field guide: challenge inspection, narrow authorization, settlement vs. delivery evidence, operational controls.
• Machine manifest: squeezeos-api.onrender.com/.well-known/x402 (verified live September 22, 2026).

What sources verify these claims?

These claims draw on the dev.to monetization guides, xpay.sh, ProBlocks’ live x402 per-call billing on Base at 0.001 USDC/call, Circle’s Facilitator Service, and SML’s live x402 manifest and mcp-x402 handshake.

• dev.to — "How to Monetize MCP Servers in 2026: The Complete Developer's Guide" (AgenticMarket) — reviewed March 2026
• dev.to — "How to Monetize an MCP Server — Payment Links, Guardrails, and Scoped Tokens" — accessed September 22, 2026
• xpay.sh — "Monetize Your MCP Server: Pay-Per-Tool Billing" — accessed September 22, 2026
• ProBlocks live x402 per-call billing on Base, 0.001 USDC/call — EINPresswire, September 17, 2026
• Circle Facilitator Service for x402 USDC payments (agents pay without separate gas wallets) — announced September 19, 2026; via coindoo.com, September 20, 2026
• SML x402 manifest and mcp-x402 handshake — fetched live, September 22, 2026

What do people ask about monetizing MCP servers with x402?

People ask how MCP servers charge per call, whether Stripe or user accounts are needed, what a 402 payment challenge contains, and how AI agents pay without holding gas tokens.

Q: How do MCP servers charge per call?

A: With x402 per-call billing: the server answers each unpaid tool call with a 402 Payment Required challenge carrying price, asset, network, payTo address, and expiry. The agent's wallet signs the authorization and retries the same call; a facilitator settles on-chain and the server returns the tool result with a receipt.

Q: Do I need Stripe or user accounts to monetize an MCP server?

A: No. x402 billing is account-free — no API keys, no subscriptions, no checkout pages. Stripe-based approaches (payment links, $19/mo tiers) work for humans but force agents through human-shaped checkout; per-call x402 pricing is built for machine buyers.

Q: What does a 402 payment challenge contain?

A: Price, asset, network, payTo address, expiry, and resource binding. On HTTP transports it travels in a PAYMENT-REQUIRED header or the 402 body; the buyer answers with a PAYMENT-SIGNATURE header and keeps the PAYMENT-RESPONSE receipt.

Q: How do AI agents pay without holding gas tokens?

A: A facilitator verifies the signed payment authorization, broadcasts the transaction, and pays the network fee — the agent only signs. SML's live manifest points at the Coinbase CDP facilitator; Circle's Facilitator Service (September 2026) does the same for USDC across Arc, Base, and Polygon PoS.

SCRIPTMASTERLABS · Truth First. Proof Always. Pay Only for Accepted Delivery.