2025-06-14 · agentmail

x402 Payments and Compliance for AI Agents

x402 lets agents pay per-call in USDC. Here is how to keep those agent-to-agent payments compliant with OFAC sanctions screening.

x402 is the payment primitive built for agents: a standardized way for one agent to pay another a small amount of USDC for a resource, in a single HTTP round trip. It is elegant — but every x402 payment is still a funds transfer, which means it is still in scope for sanctions screening.

Why per-call payments do not escape OFAC

The size of a payment does not change the rule. A $0.01 USDC transfer to a sanctioned wallet is still a prohibited transaction. Because x402 is designed for high-frequency, autonomous micro-payments, an un-screened agent can rack up many violations in minutes.

The right pattern: screen, then pay

Treat the sanctions check as the gate before the x402 payment. agentmail accepts an x402 payment itself for the screen, so an agent with no API key can still run a paid, per-call sanctions check — and then decide whether to proceed with the downstream payment it was about to make.

curl -H "X-PAYMENT: <x402-facility>" "https://sanctionsai.dev/sanctions?wallet=0x098B..."

The free tier also covers 50 checks/day by IP with no payment at all. Add compliance to your x402 agent in minutes.

Screen your agents payments

Free tier, 50 checks/day. Add compliance before money moves.

Try the free checker  See pricing