Guide · AI agents · as of 20 November 2026

AI agents can now pay for things. Five checks before yours does.

On 19 November 2026, Amazon Web Services let AI agents buy software from AWS Marketplace and pay for it per request, with the charge landing on the company’s normal AWS bill. The payments run on x402, an open standard that turns a web request into a purchase: the seller answers “payment required”, the agent pays, and the request goes through. Until now an AI agent could read, write and click. Now it can spend, without a person typing a card number. That makes one question urgent for any business running agents: where does the spending limit live, and can the agent get past it? This guide covers what changed, how x402 works, what we found when we checked our own caps, and five checks.

What AWS announced

An agent with a company wallet.

AWS says agents built on its AgentCore service can now find selected AWS Marketplace products and buy them, paying per request in US dollars. No crypto wallet is needed: the charge settles on the existing AWS bill. Before an agent buys anything, the customer can set spending limits, a list of approved sellers and other guardrails, and the company’s Private Marketplace rules still apply. Each transaction appears in AWS CloudTrail and Cost Explorer. Sellers take part by adding the AWS Marketplace x402 SDK to their listing. AWS has not published a list of regions beyond “wherever AgentCore payments is available”, and the announcement does not say how fine the limits go, for example per task or per day. Read the AWS documentation for your own account before you rely on a particular kind of limit.

How x402 works

Payment required.

Every web server has long had a status code that almost nobody used: 402, Payment Required. x402 puts it to work. When a request arrives without payment, the server answers 402 with a price. The agent pays and sends the request again, this time with proof of payment, and gets its answer. The x402 site describes it as an open, neutral standard, settled in stablecoins for a small network fee. AWS settles the same flow on your AWS bill instead. The point for a business is speed and size. A person buys software a few times a year after a meeting. An agent can make hundreds of small payments an hour, each too small to notice on its own. A mistake, a loop or a prompt injection that tells the agent to “buy the premium data feed” can add up before anyone reads a report.

Why stolen AI keys are already being spent by attack agents

What we found in our own caps

Three hard caps, one that multiplies.

We run AI agents and AI chat assistants, so on 20 November we checked where each one’s spending stops. Our three scheduled agent jobs each start with a dollar cap and a time limit given to the program that runs them, not to the agent: 4 dollars and 30 minutes for the nightly tester, 4 dollars and three hours for the weekly fixer, 6 dollars for the monthly review. When the cap is reached, the run stops, whatever the agent wants. One of our website chat assistants has a daily budget in its code that refuses new requests once it is spent. The gap: the count is kept separately by each running copy of the server, so when traffic spins up several copies, the real ceiling is several times the one we set. The fix is a shared counter all copies read, which is on our list. The lesson we took: a limit is only as real as the place it is counted.

AI agents in Dubai, built with limits that sit outside the agent

Five checks before an AI agent spends your money

Run these this week.

  • 1. List every agent that can spend. That means any agent holding a payment card, an API key on a paid account, or cloud permissions that can buy. Test: for each AI key your company uses, name the account it bills and the person who owns it.
  • 2. Put the ceiling outside the agent. A sentence in the prompt saying “spend no more than 50 dollars” is not a limit. A spending cap in the provider’s billing console, or a budget the cloud enforces, is. Test: find the figure at which each account stops charging, not just the one at which it sends an email.
  • 3. Cap each task and each day, not only each month. A monthly limit lets one bad night spend the whole month. Test: work out the most a single runaway run could spend before something stops it, and write the number down.
  • 4. Let agents pay only sellers you picked, and ask a person above a set amount. Test: check whether your agent could pay a seller nobody in your company has approved, and what amount triggers a human sign-off.
  • 5. Keep the record yourself and match it to the bill. Every agent payment should be in a log you own, tied to the job that made it. Test: take last week’s AI and cloud charges and match each one to a named job. Anything you cannot match is the first thing to look at.

Questions

Questions about AI agent payments.

  • What is x402?

    x402 is an open standard for paying over the web. A server that wants payment answers a request with HTTP status 402, Payment Required, and a price; the client, often an AI agent, pays and repeats the request with proof of payment. The x402 site describes settlement in stablecoins; AWS settles x402 purchases on the customer’s AWS bill.

  • Can AI agents make payments?

    Yes. Since 19 November 2026, AWS lets agents built on Amazon Bedrock AgentCore buy selected AWS Marketplace products and pay per request in US dollars, within spending limits and approved sellers the customer sets. Other payment companies are building similar systems.

  • What does agentic payments mean?

    Payments started and completed by an AI agent on someone’s behalf, without a person entering card details for each one. The person or company sets the rules in advance, such as how much, to whom and for what, and the agent pays within them.

  • How do I set a spending limit for an AI agent?

    Set it where the agent cannot change it: in the billing console of the AI or cloud provider, in the program that starts the agent, or in a payment service with its own limits. Then cap each task and each day, allow only approved sellers, and keep a record of every payment you can match to your bill.

  • Do I need crypto to use AI agent payments on AWS?

    No. AWS says x402 purchases on AWS Marketplace settle on the customer’s existing AWS bill in US dollars, with no crypto wallet required.

  • Does this matter to a business in the UAE?

    If your company runs AI agents on cloud or AI accounts that bill your card, an agent’s spending is your company’s spending. The same five checks apply wherever the agent runs: know which agents can spend, put the cap outside the agent, cap per task, approve sellers, and match the record to the bill.

Sources

read 20 November 2026

Check it at the source.

  1. AWS: AWS Marketplace now supports agentic payments with AgentCore (the announcement of 19 November 2026: spending limits, approved sellers, CloudTrail and Cost Explorer)
  2. x402: the open payment standard (how the 402 Payment Required flow works)
  3. BRev Digital: AI agents are stealing AI keys to pay for their own attacks (why a spending cap is also a security control)
  4. BRev Digital: how to stop an AI agent that is already running (our kill-switch guide, tested six ways)

A question?

Know what your agents can spend?

Tell us which AI agents and AI accounts your team runs. We will list what each one can spend, check where its limit actually lives, and set caps it cannot talk its way past.

Talk to usWhatsApp +971 50 728 5494hello@brevdigital.com