AI agents that browse the web on someone’s behalf keep hitting the same wall: content or data that costs money. Amazon Web Services and Anchor Browser say they now have a way past it. In a post on the AWS Machine Learning Blog on 13 October 2026, AWS said Anchor Browser now works with Amazon Bedrock AgentCore payments “so that AI agents can pay for x402-protected pages and APIs autonomously”.
The product, Anchor Browser with Agentic Payments, was “Developed in collaboration with the AWS Generative AI Innovation Center Partner Agent Factory, it’s now available on AWS Marketplace,” according to AWS.
What HTTP 402 and x402 mean
Every time a browser asks a website for something, the server answers with a short status code. Most people know 404, “Not Found”. Code 402 means “Payment Required”: the server is saying “this costs money, pay first.” It has existed in the web’s rules for decades but was rarely used, because there was no standard way for a program to actually pay.
x402 is an attempt to fill that gap. AWS describes it as “an open standard for HTTP-based machine-to-machine payments.” In plain terms: when a program asks for a paid page or API, the server replies with a 402 plus a price tag. AWS says the reply includes “the amount, accepted payment methods, and payment address”. The program pays, sends the request again with proof of payment attached, and gets the content. No sign-up form, no card checkout, no human clicking “buy”. The payments are made with digital wallets, and the AWS post refers to stablecoins (cryptocurrencies designed to hold a steady value, such as a digital dollar) and USDC.
AWS gives examples of where this matters: “premium datasets charge by the query, research APIs meter by the call, and paywalled publishers gate content behind payment.” Without a way to pay, AWS says, “The task stalls and requires manual intervention.”
What the two products do
Anchor Browser is, in AWS’s words, “a cloud-based browser automation solution purpose-built for AI agents”: a real browser running in the cloud that an agent controls, keeping logins, recording sessions and offering a live view.
AgentCore payments is a managed AWS service that, according to AWS, “manages wallet connectivity, enforces configurable spending limits at the infrastructure layer, and processes payments through the x402 protocol.” AWS says it also logs “payment attempts, approvals, denials, and settlements through Amazon CloudWatch”, its monitoring service. The wallets come from outside providers: “either Coinbase Developer Platform (Coinbase CDP) or Stripe Privy.”
How a payment happens
AWS sets out the steps. When a browser session starts with payments switched on, Anchor opens a matching payment session in AgentCore with a set budget. If a page or API answers with 402, Anchor reads the price and checks it against the wallet linked to the session. AgentCore then checks the amount is within the spending limit and signs the payment through the wallet provider. AWS says: “No key material enters the browser or agent runtime.” In other words, the secret keys that control the money stay with AWS and the wallet provider, not inside the agent, where a malicious web page might try to steal them.
The browser then sends the original request again with the signed payment attached, “exactly once”, according to AWS. The seller checks the proof, “settles the transaction on-chain” (records it on a blockchain), and serves the content.
If anything goes wrong, such as a garbled price request, no compatible payment option, an empty budget or a refused payment, AWS says the browser hands “the original 402 response to the page unchanged”, so the agent’s code sees an ordinary error.
Switching it on
According to AWS, developers turn the feature on with a single setting, session.x402, which is off by default. AWS is blunt about what that means: “Enabling session.x402 authorizes the browser to make real payments from the configured payment instrument.”
AWS says existing automation scripts written with common tools such as Playwright and Puppeteer do not need changing, and that Anchor agents also get a built-in x402 tool for paid API calls, not just web pages. To help agents find paid services, AWS says AgentCore offers a Coinbase “x402 Bazaar” directory through its AgentCore Gateway.
Who pays, and how
Although the seller is paid on a blockchain, the customer may never touch crypto. AWS says: “Anchor Browser settles third-party x402 charges in credits on the same invoice as browser session time.” According to AWS, that means “no separate crypto custody to manage, no USDC balance to monitor, and no on-chain settlement for the finance team to reconcile.” AWS did not give prices, and points developers to Anchor’s documentation for specific spending and time limits.
What this means
- Paid content for agents is becoming plumbing. AWS and Anchor are pitching payment as a setting on the browser, not something each developer has to build.
- Spending caps are the safety net. AWS itself warns that without hard limits, “a bug, retry loop, prompt injection, or inadvertent access can trigger unintended payments.” Budgets enforced outside the agent are its answer.
- x402 keeps gaining big backers. With Coinbase’s and Stripe’s wallet services plugged in, and AWS selling the service, the protocol is moving from experiment toward mainstream cloud tooling. These are the companies’ claims; there are no public usage figures yet.
Related stories
- AI Agents Are Learning to Spend Money: The Payments Infrastructure Race
- The Claude Code Leak Revealed Coinbase x402 Payment Protocol And Nobody Noticed
- American Express Publishes “Intent Intelligence” to Stop AI Agents Buying What You Did Not Approve
- Fences for AI Agents: Microsoft’s Execution Containers and AWS’s Strands Box
- AWS Makes Its AI/ML Skill a Core Part of the Agent Toolkit, Taking Coding Agents From Inference Tuning to Full SageMaker Workflows
Sources
- AWS Machine Learning Blog, “Building agents that transact with Anchor Browser and AgentCore payments”, 13 October 2026. https://aws.amazon.com/blogs/machine-learning/building-agents-that-transact-with-anchor-browser-and-agentcore-payments/
