Agent payments, x402
Let your agent buy the data it needs, one request at a time
With x402, an API can ask for payment in the middle of a request and the agent pays on the spot. That's useful right up until nobody knows what the agent spent or why. VeriProof checks each payment against your spending rules before the wallet signs. Routine purchases go through, and anything outside the limit goes to the person who owns the budget.
What happens when an API asks for payment
The API answers with 402 Payment Required
The agent asked for a market data report. The provider replies with a price, the network it accepts, and the facilitator that will settle the payment.
Your application asks VeriProof first
Before the wallet signs anything, the application sends the price, network, and provider to VeriProof with a policy check.
Your rules decide
A $4 report from an approved provider is allowed. A $400 report, a provider nobody has approved, or a network your treasury doesn't use is paused for the budget owner.
The wallet pays and the agent carries on
Once the payment is allowed or approved, your wallet signs and the facilitator settles it. The agent gets its data.
The record ties it together
The decision, any approval, and the settlement status the facilitator reports sit in one record the budget owner and compliance can both open.
Spending rules teams start with
- Allow purchases under a set amount from providers on your approved list.
- Send anything over that amount, or from a new provider, to the budget owner.
- Pay only on the networks your treasury supports, such as Base, Polygon, or Solana.
- Keep test wallets and live funds apart, so a sandbox route never spends real money.
Try a new or changed rule in Shadow to see what it would have decided before it applies. When an engineer changes a rule for a production agent, an administrator or compliance officer approves it first.
What your developers connect
Your wallet, your facilitator, and the x402 client stay as they are. The application wraps the payment in a policy check from the VeriProof core SDK, so a paused or denied payment never reaches the wallet. The SDKs include field names for x402 events, networks, and settlement status, so rules and records use the same terms across agents. No separate x402 package is needed.
Paying through pay.sh, checking out under an AP2 mandate, or paying suppliers in stablecoins? See pay.sh, AP2, or stablecoin payments, or read how VeriProof handles agentic payments as a whole.