Munition
Docs menu

Two ways to pay

How agents and developers pay for Munition services: a Munition subscription, coming with billing, or x402 per call from the agent's own wallet.

Munition sells small paid services to agents: web search and page reading, HTML to PDF, file uploads, flight search and hosted forms. There are two ways to pay for them, and both reach the same services at the same prices.

Way to pay Who it's for Account needed How you pay Where to start
1. Munition subscription (coming with billing) People and teams using Munition in Claude, ChatGPT or their own code Yes: an API key, or the remote MCP connector https://api.munition.io/mcp with one-click OAuth A subscription on your Munition account Pricing (early access)
2. x402 per call Agents with their own wallet, and the developers who build them No USDC per call from the agent's wallet, on Base, Polygon, Arbitrum or Solana Pay per call with x402

When to pick which

  • Pick the subscription if a person or a team is behind the agent: you want Munition inside Claude or ChatGPT, or behind an API key in your code, without anyone handling a wallet. Billing is not live yet; Pricing has early access.
  • Pick x402 if the agent pays for itself: it already holds USDC, you want no account, no key and no sign-up, and each request should carry its own payment. Any x402 client works, and every price is stated in the 402 before anything is signed.

1. Munition subscription

Coming with billing. The subscription puts Munition behind one account: an API key for your own code, or the remote MCP connector https://api.munition.io/mcp in Claude, ChatGPT and other MCP clients, connected with one-click OAuth. Plans and early access are on Pricing.

The connector and account tokens exist today, but until billing ships they run on the account balance described below, not on a subscription.

2. x402 per call

x402 is an open HTTP payment protocol. Every paid x402 route of Munition answers an unpaid request with 402 Payment Required and the price in a PAYMENT-REQUIRED header (MPP routes use WWW-Authenticate instead, and account routes use Bearer authentication). The agent signs a USDC payment from its own wallet and sends the same request again with a PAYMENT-SIGNATURE header; the API settles the payment and returns the result.

Many routes are also sold over MPP, under /v1/mpp/*, with the same input, result and price. See MPP routes.

Account balance (current)

Until billing ships, the account path runs on an anonymous Munition account funded with USDC. This is how the remote MCP connector and the @munition/mcp package pay today:

  • The remote MCP connector (https://api.munition.io/mcp): the OAuth consent page creates an anonymous account in one click. Paid tools are charged to that account's balance, and return a top-up link when it is empty. Setup for each client is in the connect guide.
  • The local @munition/mcp package: it creates an anonymous account and keeps its account token in ~/.munition/config.json, then calls the account routes with Authorization: Bearer <token>.
  • The balance is USDC in the account's own wallet on Base. Top-ups add USDC on Base, sent directly or bought by card where an onramp is available. Each paid call settles from that wallet over x402 on Base, at the Account balance prices in the price tables.

This is the current account path, not the subscription: it needs USDC to start, and it is documented here so that agents already using it know how it works.