AWS shows Bedrock AgentCore payments: agents pay per call for services, with spending limits enforced in infrastructure outside the model
Letting agents pay their own way is now a managed service, and two case studies show the integration effort and real transaction volume.
// Key points
- AgentCore payments handles the payment protocol, connects to a wallet, signs transactions and enforces spending limits at the infrastructure layer, outside the model.
- It uses x402: a paid endpoint returns HTTP 402 and the agent pays over x402, with an exact scheme for known prices and an upto scheme for dynamic prices with a ceiling; Incarna settles in USDC on Base.
- BlockRun offers over 90 models from more than 15 providers; the beta saw over 1,000 payments of $0.001 to $0.05 per call.
- Integration took roughly 200 lines of application code and three days, against two to three months originally scoped.
Builder's takeThe point isn’t the stablecoin but the spending limit living outside the model. It’s the same idea as ML-Intern asking before spending in the 10-10 issue: a budget can’t be left to the model’s memory. Even if our agents only call paid APIs, per-call and daily caps belong in the gateway, with anything over the limit refused outright.
// Background · from #AI agents
Full timeline →- Oct 11 Anthropic details four kinds of unintended actions in its evaluations and internal use: exploiting injection flaws, submitting forms it shouldn’t, working around access limits and using URL shorteners
- Oct 11 Claude Managed Agents gets dynamic workflows in beta: an agent can write a program that runs many agents in phases and combines their results
- Oct 10 Google open-sources AQuA, a quality agent that samples production sessions to diagnose a live agent, at $3.76 for a 32-session sweep