AWS Bedrock AgentCore pay-per-use feature goes live
What happened
On 9 October 2026, the AWS Machine Learning Blog reported that Incarna used Amazon Bedrock AgentCore payments to let AI agents pay BlockRun per use via x402 for model inference, cutting the work to add x402 payment support from months to days and putting an end-to-end pay-per-use inference flow into production. On 14 October 2026, AWS published a tutorial on integrating Anchor Browser with AgentCore payments, letting AI agents automatically complete x402 protocol payments when they hit HTTP 402 Payment Required and continue their tasks. The current state is that enterprises have put pay-per-use inference flows into production, and AWS has further published an integration tutorial for automatic agent payments.
Written by AI from the reports · updated 2 d ago
Developments
- Oct 14 04:10 · 1 reportsAWS launches AgentCore payments to support autonomous agent paymentsAWS Machine Learning Blog：Building agents that transact with Anchor Browser and AgentCore payments
- Oct 9 02:33 · 1 reportsAWS launches pay-per-use feature for Bedrock AgentCoreAWS Machine Learning Blog：Pay-per-inference for AI agents: How BlockRun and Incarna use Amazon Bedrock AgentCore payments
Timeline
Follow the reports to see the event from each side.
- AWS Machine Learning BlogBuilding agents that transact with Anchor Browser and AgentCore payments
Learn how the AWS Generative AI Innovation Center Partner Agent Factory and Anchor Browser built AI agents that autonomously pay for x402-protected web resources and APIs. Amazon Bedrock AgentCore payments checks budgets, signs transactions, and retries requests without exposing wallet credentials to the agent runtime.
- AWS Machine Learning BlogPay-per-inference for AI agents: How BlockRun and Incarna use Amazon Bedrock AgentCore payments
Amazon Bedrock AgentCore payments gives AI agents a managed way to pay for services on demand, with spending limits enforced by the infrastructure. See how Incarna's agents pay BlockRun for model inference one request at a time over x402, cutting the work of adding x402 payment support from months to days.
Heat of this event
Current heat 3·Peak in the comparable range 9（Oct 14 07:00）·Change over 24 hours in the comparable range -50%
The trend compares only the same accounts observed without a break, so its range can be narrower than the current heat count. Move the pointer or tap the chart to see each hour; with a keyboard, use the left and right arrow keys.