For MCP / tool authors

Monetize an MCP server

Charge per tool call on your MCP server. Pair MCP with x402: each tool exposes a price, the agent’s runtime pays in USDC, and you settle per invocation — without building a billing system or handling wallets yourself.

Start free How it works

MCP standardises how an agent discovers and calls your tool; x402 standardises how it pays. Together they let you put a price on individual tool calls.

You expose the 402 correctly with a price; the agent runtime handles funding, paying, and attaching proof. Your job is to register the tool’s route and price.

How it works

01
Register each tool’s route
Add the tool name and price in the dashboard. Start in sandbox.
02
Return a 402 per call
Each tool call quotes its price as a signed x402 challenge.
03
The runtime pays
The agent’s runtime pays in USDC and retries with proof; the tool runs.
04
Flip to live
Change one env var from sandbox to live — no code changes.

Charge per tool call, not per subscription
No wallet handling — the agent runtime brokers payment
Works alongside your existing MCP server
Test mode before a single real cent moves

FAQ

Do I have to handle the agent’s wallet?

No. You expose the 402 with the price; whichever runtime the agent uses funds the payment and attaches the proof on retry.

Can I price tools differently?

Yes. Each tool’s route has its own price, set in the dashboard.

Monetizing an MCP server with x402 What is MCP? All use cases