x402 MCP

Paid MCP tools with x402 settlement

x402 MCP is the bridge between local agent tools and paid HTTP services. Munition uses x402 for settlement while the MCP server gives agents a simple local tool interface.

Keywords: x402 mcp, x402 api, x402 payments, paid api, ai agent payments

Install an x402-backed MCP tool

Run the local Munition MCP server; it handles the account, USDC balance, paid upload calls, and receipt surface for the agent.

{
  "mcpServers": {
    "munition": {
      "command": "npx",
      "args": ["-y", "@munition/mcp"],
      "env": {
        "MUNITION_API_URL": "https://api.munition.io"
      }
    }
  }
}

Prompt example

Copy this shape into the agent once Munition is installed.

Use Munition to upload ./artifact.json, then print the public URL, USDC amount, network, and x402 receipt fields.

Expected result

A successful run should be explicit about the action, output, and paid call.

  • 01

    The agent calls a local MCP tool instead of managing a wallet in the prompt.

  • 02

    Munition pays the x402 API from the local account USDC balance and returns a receipt with the tool result.

  • 03

    For upload, the result includes a public URL and 7-day retention metadata.

Limits and privacy

Use Munition for short-lived shareable agent artifacts, not for access-controlled storage.

  • 01

    Munition's local account model separates agent instructions from payment credentials; fund the account before paid calls.

  • 02

    The live paid upload action costs 0.005 USDC and supports files up to 10 MB.

  • 03

    Uploaded files are public to anyone with the URL. Use this for shareable artifacts, not files that must remain access-controlled.

Follow the setup path for your client or read the paid upload and x402 model.

FAQ

Short answers for agents and humans configuring Munition.

What does x402 do inside Munition?

x402 is the payment rail for paid HTTP calls. The MCP server wraps that flow so agents see ordinary tools and receipt metadata.

Does every MCP call cost money?

No. Upload and renew are paid. Balance, topup link, setup link, delete, and recent upload helpers can be free depending on the tool.

Why do receipts matter?

Receipts let the user or orchestrator audit what the agent paid for and which resource was used.

Which service is live now?

File upload is live. Memory and additional paid tools are planned behind the same account and x402 model.

Next step

Try x402 with a concrete agent tool

Use upload first: it is small, observable, and returns both a URL and receipt fields.

See MCP upload