Munition
Docs menu

Networks and assets

The networks and assets Munition's server accepts for x402 and MPP payments, and where an agent reads them in the live payment challenge.

Munition is paid in one asset, USDC. x402 routes accept it on four networks, MPP routes on three:

Network CAIP-2 id Asset Token address x402 MPP
Base eip155:8453 USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 yes yes
Polygon eip155:137 USDC 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359 yes yes
Arbitrum One eip155:42161 USDC 0xaf88d065e77c8cC2239327C5EDb3A432268e5831 yes yes
Solana solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp USDC EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v yes no

All four are mainnets. On Solana the token address is the USDC mint. Amounts are always in USDC atomic units, with 6 decimals: 4000 is 0.004 USDC, 1000000 is 1 USDC.

x402

Every paid x402 route offers all four networks, one entry per network in the accepts list of its 402, all for the same amount. The agent picks the one its wallet can pay.

  • Scheme: exact on every network, a fixed price per call.
  • Base, Polygon and Arbitrum One: the payment is an EIP-3009 TransferWithAuthorization signed by the payer. The challenge gives the EIP-712 domain in extra: name is USD Coin and version is 2 on all three.
  • Solana: the payment is a USDC transfer transaction partially signed by the payer. extra.feePayer names the facilitator's account, which is the transaction's fee payer: the facilitator, not the payer, pays the network fee.
  • Time limit: maxTimeoutSeconds is 300 (five minutes). On the EVM networks, x402 clients use it as the validity window of the signed authorization.

The decoded challenge, with all four entries, is on Pay per call with x402.

MPP

MPP routes (/v1/mpp/*) accept USDC on Base, Polygon and Arbitrum One, as an EIP-3009 authorization that Munition submits on chain. An unpaid MPP request gets a WWW-Authenticate: Payment challenge whose charge asks for USDC on Base (currency eip155:8453/erc20:0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The three networks are listed as supportedNetworks in https://api.munition.io/.well-known/mpp.json, and they are the only ones the API takes: a credential for any other network, a testnet included, is refused with 402 invalid_payment (details.reason is mpp_unsupported_network) before anything is settled. The credential must also keep the challenge's amount, its USDC token and its recipient; otherwise it is refused with a 402 before anything is settled.

Account balance (current)

The account path, used today by the remote MCP connector and the @munition/mcp package, works differently: the account has its own USDC wallet on Base, and each paid call settles from it over x402 on Base. Top-ups add USDC on Base, sent directly or bought by card where an onramp is available. See Account balance (current).

Where an agent reads them

  • In the 402 itself. The accepts list of an x402 challenge, or the charge request of an MPP challenge, is authoritative: it names the networks, assets, amount and recipient for that call.
  • In the discovery documents, before calling: https://api.munition.io/.well-known/x402.json for x402 and https://api.munition.io/.well-known/mpp.json for MPP. The server reads the payment from PAYMENT-SIGNATURE and answers with PAYMENT-REQUIRED and PAYMENT-RESPONSE, as described on Pay per call with x402; the discovery documents use the same names.