Amazon Web Services added AWS Billing to Amazon Bedrock AgentCore payments on November 19, letting agents buy individual requests from participating AWS Marketplace sellers in US dollars. Charges appear on the developer’s AWS bill. The update extends AgentCore payments, which became generally available in August, with a purchasing path that does not require a stablecoin wallet.
AgentCore payments turns a quoted request into an AWS charge
A participating seller returns an HTTP 402 response containing a signed price quote. The agent passes that quote to AgentCore payments, which checks the payment session’s remaining budget and returns a token. The agent retries its request with the token to receive the purchased result.
At launch, AWS Billing supports x402’s exact scheme: the seller quotes a fixed price for each request. The first purchase creates an agreement between the AWS account and that seller; subsequent purchases are tracked against it and appear as Marketplace line items.
That gives agents running automated workflows a way to acquire a paid tool response during a task, with the purchase recorded in the account’s existing billing system.
Availability depends on the seller and the integration
The feature covers x402-enabled Marketplace offerings, rather than every API an agent might encounter. Sellers must register with AWS Marketplace and integrate its x402 SDK, going through the marketplace’s registration and review process.
Siteimprove announced its Accessibility Agent as a launch offering on November 19. Its announcement describes per-request access for agents performing accessibility checks and fixes, billed through the buyer’s AWS account. That is a concrete catalog example, rather than evidence of how reliably an agent will complete an accessibility project.
Developers configure an AWS Billing connector and the required service-linked role. An optional Marketplace connector in AgentCore Gateway lets agents discover listings and endpoints. Existing AWS authentication and setup remain necessary even though the payment path removes separate vendor API keys.
Spending permissions remain part of the deployment
AWS says developers can set spending limits and approved sellers, with the payment service enforcing each session’s cap. Private Marketplace restrictions also apply. Transaction records are available through AWS’s billing and audit tools, including CloudTrail.
Constellation Research places the launch within AWS’s broader procurement push, which also adds capabilities for discovery, checkout and deployment. For developers, the narrower change is useful: buying a tool response can become an agent action, with its price and spending authority configured before the request runs.