When AI Agents Pay and Sellers Monetize: Building x402 Apps on AWS — Anil Nadiminti, AWS
AWS is separating agent payment policy from model execution: AgentCore handles wallets and limits, while WAF meters bot access. The useful pattern is deterministic spend control at the edge.
The talk contrasts a **$0.25 minimum fee plus 2.5%** with agent calls costing around a tenth of a cent. AWS AgentCore Payments adds wallet connectors, session limits, expiry, observability, and x402 support; WAF can distinguish **over 650 bot types** and price traffic by identity or intent.
Keep payment execution on a deterministic path outside the model. Set hard session budgets and expirations, trace each purchase, and apply monetization at the edge so existing content origins do not need wholesale changes.
The talk contrasts a **$0.25 minimum fee plus 2.5%** with agent calls costing around a tenth of a cent. AWS AgentCore Payments adds wallet connectors, session limits, expiry, observability, and x402 support; WAF can distinguish **over 650 bot types** and price traffic by identity or intent. Keep payment execution on a deterministic path outside the model. Set hard session budgets and expirations, trace each purchase, and apply monetization at the edge so existing content origins do not need wholesale changes. The cited market snapshot—**$50 million across 170 million transactions**—came from a Coinbase agentic market view presented by AWS. Additional payment protocols were described as planned, so current coverage should be verified before choosing the stack.
This extends gateway engineering from controlling model spend to mediating agent purchases and monetizing seller traffic. It reinforces deterministic budgets, expiry, identity checks, and purchase traces outside the model, while the separate x402 settlement-order risk means AWS support should not be treated as proof that sellers are protected from unpaid work.