Skip to main content

Pay

An agent wallet pays in two ways: it pays x402 services, which charge per request, and it transfers USDC to an address. Every payment is checked by Keyban against the spending policy before it is signed, and may wait for a human as a payment intent.

From the dashboard​

You do not make payments from the dashboard: the agent does. The dashboard is where you decide what it may pay and follow what it paid.

  • Services lists the x402 services the agents can pay, and an administrator authorizes them there. See Discover services.
  • Inbox is where a payment above the approval threshold waits for a person. See Approve payments.
  • Expense tracking lists what was paid. See Track spending.
  • The limits and the destination rules are set on the wallet page. See Control spending.

What the agent can do​

Find and price a service​

Before it pays, the agent finds a service with discover_x402_services and checks its price and parameters with x402_info, without paying. See Discover services.

Pay an x402 service​

x402_pay fetches the resource and pays automatically. It takes the URL, and optionally the method, headers, body, a maxAmount in USDC and an intentId.

  • maxAmount is a spend ceiling: Keyban refuses the payment if the service asks for more.
  • Keyban reads the real price from the service itself and checks the domain and the amount against the policy. The agent does not need to ask the user to confirm each payment: the policy is the authorization.
  • If the amount is above the approval threshold, nothing is signed and the payment waits. See below.
  • The tool returns the body of the response.

Transfer USDC​

transfer_usdc sends USDC from the wallet to an address. It takes the recipient to and the amount value as a decimal in USDC, such as 1.5, with at most six decimals. It works on both networks of agent wallets, Base mainnet and XDC mainnet, which have a canonical USDC contract.

The recipient is checked against the destination rules, and the amount against the caps and budgets. An agent can have only one transfer in flight at a time: a second one is refused with policy/intent-in-flight until the first is signed or cancelled. Once a transfer is sent, a USDC transfer cannot be recalled, so the agent should not send it again unless the user asks. list_expense_transactions gives the transaction hash.

Sign a message​

sign_message is not a free-form signing tool. Every signature of an agent wallet goes through Keyban, which co-signs only what matches a payment intent it approved. sign_message creates no intent, so the hash of an arbitrary message matches none, and Keyban refuses the request with policy/intent-not-found. It is also refused with policy/missing when the wallet has no policy, and with policy/emergency-stop when the wallet is paused. In practice an agent should not rely on it to sign a message for a third party. The reasons are explained on the Refusal reasons page.

Wait for an approval, or cancel​

When a payment is held, the answer carries the intent's identifier and tells the agent to wait. In agent apps that show the approval card, x402_pay and transfer_usdc wait for the decision on their own. Elsewhere:

  1. The agent tells the user that a payment is waiting for them in the Inbox.
  2. It calls wait_for_intent, which blocks until a wallet operator decides on any held payment (up to 45 seconds) and returns the intent that changed and those still waiting. It calls it again if it returns still waiting.
  3. Once the intent is approved, it calls the same tool again with the same arguments, passing the intentId for x402_pay.

An x402 intent is valid for the window the service allows, commonly a few minutes, and expires if the approval comes too late. The agent then starts again. A USDC transfer intent has no expiry of its own. cancel_intent withdraws the agent's own request and releases the budget it holds; it never authorizes anything. The agent should never start a second payment for the same purchase while the first one is held.

The tools are listed with their inputs on the Wallet MCP tools page, and the reasons a payment can be refused on the Refusal reasons page.

Limits​

  • x402 payments work on Base mainnet and XDC mainnet. The wallet pays on its own network and never follows a service to another chain.
  • x402: only the exact scheme, only USDC, in the amount the service states.
  • USDC is the only token a wallet pays with. Other tokens Coming soon are not available yet.
  • The organization has a monthly transaction quota shared by its wallets. Once it is reached, payments are refused with policy/transaction-quota-reached. See Plans and quotas.
  • A paused wallet refuses every payment with policy/emergency-stop.
  • Message signing is subject to the same policy check: sign_message is refused when no approved intent matches (policy/intent-not-found), when the wallet has no policy (policy/missing) and when it is paused (policy/emergency-stop). See Refusal reasons.
  • A refused payment is final for that request. The agent reports the reason, and never splits a payment or routes it around a rule to get past a cap, an approval threshold or a destination rule.
  • Subscriptions and recurring payments Coming soon, batch payments Coming soon and escrow Coming soon are not available yet.