AWS Releases AgentCore Payments for General Availability in Amazon Bedrock AgentCore
Cloud

AWS Releases AgentCore Payments for General Availability in Amazon Bedrock AgentCore

AWS announced general availability of AgentCore payments on August 18, 2026. The fully managed service, part of Amazon Bedrock AgentCore, lets AI agents autonomously discover and pay for paid APIs, MCP servers, and paywalled content using stablecoin wallets from Coinbase CDP and Stripe Privy.

2 min read
Back to News
TL;DR
  • -AWS made AgentCore payments generally available on August 18, 2026, within Amazon Bedrock AgentCore.
  • -The service handles microtransaction payments in AI agent workflows using Coinbase CDP and Stripe Privy stablecoin wallets, with session-level spending caps enforced at the infrastructure layer.
  • -General availability adds Machine Payment Protocol support, the x402 'upto' spending ceiling scheme, a Quick Create option for Coinbase credentials, and prebuilt observability dashboards in AgentCore Observability.

AgentCore Payments Reaches General Availability in Amazon Bedrock AgentCore

AWS announced general availability of AgentCore payments on August 18, 2026. The capability, part of Amazon Bedrock AgentCore, lets AI agents autonomously discover and pay for paid APIs, Model Context Protocol (MCP) servers, and paywalled content.

What the Service Does

AgentCore payments is a fully managed service for microtransaction payments in AI agent workflows. Individual transactions are often measured in cents or fractions of a cent. Traditional payment methods impose minimum fees that make those amounts uneconomical, so the service uses stablecoin wallets instead.

It integrates with two wallet providers: Coinbase CDP and Stripe Privy. Developers supply Coinbase or Stripe Privy API keys and secrets. Credentials are stored in AgentCore Identity, which is a secrets management layer inside the platform. Agents do not receive raw credentials. AgentCore derives short-lived tokens from stored credentials to instruct the wallet provider to sign transactions.

Payment Protocols

The service supports two open payment protocols. The x402 protocol uses the HTTP 402 Payment Required status code for programmatic agent-to-merchant transactions. At general availability, support for the Machine Payment Protocol (MPP) was added. MPP is a standard co-authored by Stripe and Tempo for machine payments. Developers can pay any MPP-compatible service without writing additional integration code.

Also new at general availability is the "upto" scheme within x402. This lets an agent set a spending ceiling rather than committing to a fixed price per request. Merchants charging for token usage or other metered resources can bill for actual consumption at the end of a call.

Spending Controls

Each payment session carries two configurable caps: a maximum spend amount and an expiry time. When either limit is reached, further payment requests are denied. The budget check runs at the infrastructure layer before transaction signing. If a signing attempt fails after a budget deduction, the deducted amount is not charged to the session.

Limits can be set at both user and agent levels.

Endpoint Discovery

AgentCore exposes a curated Coinbase Bazaar MCP server through AgentCore Gateway. That server surfaces more than 10,000 pay-per-use x402 endpoints. AWS updated the server at general availability to apply curation criteria including social proof, metadata quality, and availability.

Credential Provisioning

For Coinbase, AWS added a Quick Create option directly within the AgentCore console and CLI. It lets developers provision Coinbase credentials without leaving the platform. For Stripe Privy, developers obtain credentials from the Privy dashboard and supply them to AgentCore payments.

Observability

AgentCore payments automatically generates spans and metrics for every data plane API call. Spans follow the naming pattern Bedrock.AgentCore.Payments.<Operation> and are viewable in AWS X-Ray. Metrics including payment success count, payment failure count, spend amount, active sessions, and payment latency are published to Amazon CloudWatch with dimensions for operation, payment manager, connector, agent name, and currency.

AgentCore Observability includes prebuilt dashboards showing transaction success rates and average transaction values across agents, payment sessions, and time periods.

Access Paths

Developers can reach the service through the AWS CLI, AWS SDKs, AgentCore SDK, and AgentCore CLI. The AgentCore CLI agentcore add payment-manager and agentcore add payment-connector commands scaffold payment resources and prompt for required configuration. At runtime, payment processing integrates with Strands Agents and LangGraph.

Sources and supporting resources
Previous
When Production Status Lives in Emails and Spreadsheets: Choosing the Right Fix
Next
Fragmented Operating Records: How to Diagnose and Fix the Problem

Get Business Technology Updates

Practical guidance on complex operations, integration, portals, analytics, automation, custom software, trusted records, and fit-for-purpose engineering.

No spam. Unsubscribe anytime.