Vibeleaderboard
← All Intel
Intel / article

AI agents don't just reason anymore. They transact. Cloudflare's Monetization Ga

Source
aws.amazon.com
Author
Cloudflare
Date

Context

Cloudflare says that agents built on Amazon's AgentCore Payments can now pay for resources behind its Monetization Gateway, which lets owners of content, APIs and servers charge agents per request over the protocol. Cloudflare supplies the seller side. AWS's general-availability announcement describes the buyer side: integrations for frameworks that handle an HTTP 402 Payment Required response inside the agent's execution loop, so the agent can pay and keep working without a person stepping in.

The money sits in stablecoin wallets from Coinbase or Stripe Privy, which end users fund by card or USDC and must authorize the agent to spend. Spending is capped per payment session: each agent interaction can be given a maximum spend and an expiry time, and AgentCore rejects any payment that would push the session past its cap before signing it. AWS says this check is deterministic and runs at the infrastructure layer, because agents can misread a response as permission to spend or repeat a payment after an unexpected retry. The agent never sees the raw wallet credentials. Cloudflare's own Monetization Gateway announcement covers the seller side in more detail.

Terms in this piece · Glossary
  • MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
  • x402 — A payment protocol built on HTTP's long-unused 402 status code, letting a server charge per request so software agents can pay without an account.
  • AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
Read the source aws.amazon.com
More from Cloudflare
Recommended reads
Comments

Checking sign-in…

Loading comments…