Pricing & payments

How XRP/RLUSD pricing and x402 settlement work.

Setting a price

Each tool on your provider gets its own price, in XRP and/or RLUSD — they're independent numbers, not converted from one another. You can price a tool in just one asset if you don't want to support both; an agent calling it picks whichever you've priced, or chooses between them with the optional asset argument when both are available (see the MCP's configuration reference).

Commission

PolymitaPay takes a commission on each paid call — the dashboard shows a live "you receive" preview while you're setting prices, after that cut is applied. The rate defaults to the platform-wide setting; admins can grant a provider-specific override.

How settlement actually works

Payment uses the x402 protocol over XRPL:

  1. An agent's wallet-mcp-server calls your tool through PolymitaPay's proxy.
  2. The proxy responds HTTP 402 Payment Required with the price.
  3. The agent's wallet signs and submits an XRPL payment for that amount.
  4. The call is retried with proof of payment attached; once verified, your real MCP server's tool actually runs and its result is passed back.

You never see or handle unpaid requests as manual work — a call either settles or it doesn't happen, automatically, on every single invocation.

RLUSD

RLUSD is a stablecoin pegged to USD. If a tool is priced in RLUSD, the paying wallet needs an RLUSD trust line — wallet-mcp-server opens one automatically the first time it's needed, nothing you have to prepare as a provider.