[{"data":1,"prerenderedAt":187},["ShallowReactive",2],{"blog:\u002Fblog\u002Fcloudflare-aws-x402-paywalls":3},{"id":4,"title":5,"body":6,"date":173,"description":174,"extension":175,"keywords":176,"meta":177,"navigation":178,"path":179,"readingMinutes":180,"seo":181,"stem":182,"tags":183,"__hash__":186},"blog\u002Fblog\u002Fcloudflare-aws-x402-paywalls.md","Cloudflare, AWS, and x402 paywalls: a buy-side field guide",{"type":7,"value":8,"toc":165},"minimark",[9,24,29,36,71,74,78,90,93,97,100,130,133,137,157],[10,11,12,13,18,19,23],"p",{},"The fastest-moving part of the ",[14,15,17],"a",{"href":16},"\u002Fblog\u002Fwhat-is-x402","x402"," ecosystem is the ",[20,21,22],"strong",{},"sell side"," — the\ntooling that lets a website or API charge an AI agent per request. Infrastructure providers have\nturned what used to be a bespoke billing project into a few lines of config. That's great for\npublishers. It also means the number of paywalls your agents can hit is about to go up sharply —\nand most teams running agents have no idea what they're paying.",[25,26,28],"h2",{"id":27},"what-the-gateways-do","What the gateways do",[10,30,31,32,35],{},"The pattern is the same across providers: sit at the edge, detect an incoming agent request,\nand return an ",[20,33,34],{},"HTTP 402 Payment Required"," challenge instead of the content. The agent pays\non-chain (USDC today), retries with proof, and the edge serves the resource and settles to the\npublisher's wallet.",[37,38,39,59],"ul",{},[40,41,42,45,46,52,53,58],"li",{},[20,43,44],{},"Cloudflare"," has been the loudest here — its\n",[14,47,51],{"href":48,"rel":49},"https:\u002F\u002Fblog.cloudflare.com\u002Fintroducing-pay-per-crawl\u002F",[50],"nofollow","\"pay per crawl\""," direction and its\n",[14,54,57],{"href":55,"rel":56},"https:\u002F\u002Fblog.cloudflare.com\u002Fmonetization-gateway\u002F",[50],"Monetization Gateway"," let site owners\ncharge automated clients for access at the edge, turning the 402 status code into a real\nmonetization surface for millions of sites already behind its network.",[40,60,61,64,65,70],{},[20,62,63],{},"AWS"," is ",[14,66,69],{"href":67,"rel":68},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fmachine-learning\u002Fagents-that-transact-introducing-amazon-bedrock-agentcore-payments-built-with-coinbase-and-stripe\u002F",[50],"moving the same way",":\nAmazon Bedrock AgentCore now handles agent payments over x402, and other infrastructure players\nare giving API and content owners the same managed path to price requests from agents.",[10,72,73],{},"For a publisher, this is a checkbox. For the agent operator on the other end, every one of those\ncheckboxes is a new line item you didn't budget for.",[25,75,77],{"id":76},"the-buy-side-blind-spot","The buy-side blind spot",[10,79,80,81,85,86,89],{},"Here's the asymmetry: the sell-side gateways come with dashboards, analytics, and reporting — for\nthe ",[82,83,84],"em",{},"seller",". They show the publisher what it earned. Nobody hands the ",[20,87,88],{},"buyer"," — the team whose\nagents are spending — the equivalent view.",[10,91,92],{},"So the money leaves your wallet across dozens of these gateways, priced differently, failing\ndifferently, and you're reconstructing it after the fact from a block explorer that doesn't even\nknow which of your agents made which payment. As agentic workflows move from demos to production,\nthat blind spot stops being a curiosity and starts being a real, compounding cost.",[25,94,96],{"id":95},"what-you-actually-need-on-the-buy-side","What you actually need on the buy side",[10,98,99],{},"Whatever gateway is charging your agents, the buy-side requirements are the same:",[37,101,102,113,124],{},[40,103,104,107,108,112],{},[20,105,106],{},"Visibility"," — ",[14,109,111],{"href":110},"\u002Fblog\u002Fx402-analytics","x402 analytics"," that attribute every payment to an\nagent, a domain, and a moment in time, not a flat ledger of transfers.",[40,114,115,118,119,123],{},[20,116,117],{},"Debugging"," — the ability to catch the payments that\n",[14,120,122],{"href":121},"\u002Fblog\u002Fdebugging-x402-payments","paid but still failed",", which the seller's dashboard will never\nshow you.",[40,125,126,129],{},[20,127,128],{},"Control"," — alerts when a quiet loop turns into a spend spike, before it drains a wallet.",[10,131,132],{},"Crucially, none of this should require custody. You don't want a middleman holding your funds to\ngive you a report on them.",[25,134,136],{"id":135},"_402report-is-the-buy-side-control-plane","402.report is the buy-side control plane",[10,138,139,140,144,145,147,148,152,153,156],{},"That's the gap ",[14,141,143],{"href":142},"\u002F","402.report"," fills. Where Cloudflare and AWS work for the seller at the edge,\n402.report works for the ",[20,146,88],{},": point your agent's HTTP through the proxy with one API key and\nyou get ",[14,149,151],{"href":150},"\u002Fblog\u002Fagent-spend-observability","non-custodial"," spend insights, payment forensics, and\nalerts across ",[82,154,155],{},"every"," x402 paywall your agents hit — whoever built it. It observes the payments;\nit never holds, signs, or settles them.",[10,158,159,160,164],{},"The sell side is getting industrialized fast. Make sure the buy side — your side — isn't the one\nflying blind. ",[14,161,163],{"href":162},"\u002F#waitlist","Join the 402.report waitlist"," for early access.",{"title":166,"searchDepth":167,"depth":167,"links":168},"",2,[169,170,171,172],{"id":27,"depth":167,"text":28},{"id":76,"depth":167,"text":77},{"id":95,"depth":167,"text":96},{"id":135,"depth":167,"text":136},"2026-07-08","Cloudflare and AWS are making it trivial for publishers to charge AI agents per request with x402. Here's what those gateways do, why they leave the buy side flying blind, and what agent operators need to stay in control of spend.","md","cloudflare x402, aws x402, x402 paywall, pay per crawl, agent paywall, x402 gateway, cloudflare pay per crawl, agent payments",{},true,"\u002Fblog\u002Fcloudflare-aws-x402-paywalls",6,{"title":5,"description":174},"blog\u002Fcloudflare-aws-x402-paywalls",[17,184,185],"cloudflare","paywalls","DAKlced7X5u7PcglSq7tyem6V3x2IkopLpZ4VxA1184",1784841653120]