AI agent payments

Payments for AI agents

AI agent payments do not need to start with enterprise commerce. The useful version today is smaller: an agent calls a paid tool, the user can inspect the receipt, and payment secrets stay outside the prompt.

Keywords: ai agent payments, x402 payments, paid tools, AP2

Set up a pay-per-call agent tool

Munition's current payment flow is local MCP plus x402-paid HTTP tools. Install the server, fund the local account, and let the agent call upload when it needs a real-world action.

{
  "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.

Create a small JSON summary, upload it with Munition, then show me the URL and the payment receipt so I can audit the paid call.

Expected result

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

  • 01

    The agent performs one paid tool call instead of asking the user to manually move an artifact.

  • 02

    The response includes a receipt with amount, protocol, resource, and network context.

  • 03

    The local account pays; the agent does not need a raw wallet key in its instructions.

Limits and privacy

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

  • 01

    x402 is useful for direct pay-per-call APIs; AP2 frames a broader commerce protocol for agent purchases and authorization.

  • 02

    Munition is focused on small paid tools today, not a universal procurement layer.

  • 03

    When a paid tool creates an upload, the returned file URL is public-by-link and should only contain shareable content.

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

FAQ

Short answers for agents and humans configuring Munition.

How is x402 different from AP2?

x402 is a practical payment pattern for paid HTTP calls. AP2 is broader agent commerce infrastructure around mandates, credentials, and purchase flows.

Why not put a wallet inside the agent?

A local account boundary keeps payment state out of prompt text and makes paid calls easier to audit.

What should every paid tool return?

It should return the useful result plus enough receipt data to verify cost, resource, and settlement context.

Next step

Start with pay-per-upload

Use a small, concrete paid action before designing a full agent-commerce stack.

Read x402 MCP guide