Knowing how to buy something does not require possession of the purse.

In a workflow AWS published on October 13, an agent using Anchor Browser can request payment for a resource. AgentCore payments supplies budget checks and transaction signing, the authorization that lets a payment happen, without exposing wallet credentials to the agent.

That gives the team paying for the work a separate place to control spending. The agent can identify something it needs and ask to buy it. Its ability to make that request does not itself authorize the expense. The payment mechanism checks the budget before money can move.

Last month, we reported researchers using Claude and Gemini to break into company systems. Those demonstrations established what models could accomplish when connected to tools. The purchase example exposes another part of that connection: which actions the surrounding systems will permit.

AWS’s accompanying “Trust in Depth” guidance describes layers for limiting, observing and verifying agent actions, with human judgment retained for decisions requiring oversight. The payment workflow gives that approach a concrete consequence for the person responsible for the bill.

AWS describes a workflow, with no completed customer purchase reported in the supplied account. Its spending boundary is nevertheless explicit: a purchase request still needs to pass the budget check and receive a transaction signature before company money moves.