AWS recently made AgentCore Payments generally available, allowing agents to discover and pay for APIs, Model Context Protocol servers, and paywalled content as part of their normal workflow. LangChain has already added middleware for the same capability. If this sounds like dull plumbing, much of it is. Even so, the controls around the plumbing tell us something important about what an “agent” actually is.
A traditional application executes a payment because a developer explicitly programmed the conditions. An agent can choose the service, decide that the service is relevant to its goal, assess the price, and initiate the purchase. In that sense, it’s acting as an agent in the older, legal meaning of the term: a representative authorized to act on behalf of a principal. That authority is far more consequential than calling an API.
Now imagine asking a research agent to prepare a competitive analysis. Along the way, it finds a paid industry report (remember those?), a market-data API, and several articles behind paywalls. Interrupting you to approve every five-cent purchase would make the agent nearly useless (and, speaking from experience, might make you a little crazy). At the same time, unless you’re completely price-insensitive, you probably don’t want it deciding that a $2,000 analyst report might be helpful. What you really want is to establish an allowance: Spend up to $10 during this task, perhaps no more than $2 with any one provider, only on research-related services, and provide all receipts.
