AgentCore payments now generally available in Amazon Bedrock AgentCore

What changed

Source summary

AWS launched general availability of AgentCore payments, letting AI agents built on Bedrock AgentCore autonomously discover, access, and pay for paid APIs, MCP services, and other pay-per-use content. It integrates with Coinbase and Stripe wallets for micropayments and a Coinbase Bazar marketplace, and enforces configurable spending limits at the infrastructure level, with activity monitoring through AWS observability tools.

Why it matters to your work

Practical interpretation

Relevant if your team is building AI agents that need to autonomously buy access to third-party tools or data feeds. AWS lets you set hard spending limits before turning this on, which is the key safety control if you're considering giving an agent its own ability to spend money.

When this could help

When an agent needs to autonomously purchase access to pay-per-use APIs, MCP services, or marketplace content (for example via the Coinbase Bazaar) as part of completing a task, within a bounded, monitored spending envelope.

AgentCore payments lets an agent discover, pay for, and use metered third-party services directly, with spending limits enforced at the infrastructure layer and activity visible through AWS observability tooling - rather than the team hand-building wallet integration and guardrails themselves.

How to get started

1. Start with one of the coding assistant skills (Claude Code, Kiro, or Codex), the AgentCore CLI, or the AWS Management Console to set up AgentCore payments.

   Provider guidance ↗

2. Use Quick Create in the AgentCore console to provision Coinbase wallet credentials directly, or connect a Stripe wallet, for micropayments.

   Provider guidance ↗

3. Access the curated Coinbase Bazaar MCP server of pay-per-use x402 endpoints through AgentCore Gateway.

   Provider guidance ↗

4. Review the sample implementation in the AWS Labs AgentCore samples repository (path: 01-features/08-agents-that-transact).

   Provider guidance ↗

Build it into your routine

SCALA suggested workflow

1. Agent needs a paid data source mid-task

   An agent working through a task hits a paid API or MCP service it doesn't yet have access to, and uses AgentCore payments to pay the per-use fee and continue, within its configured spending limit.

What to check

• Spending limits are described as "configurable payment limits at the infrastructure layer," but the exact configuration mechanism is documented separately in the AgentCore payments developer guide, not on this announcement page. Source ↗
• Supports payment orchestration across the Machine Payment Protocol (MPP) and the "upto" scheme in x402 for pay-per-inference and dynamic pricing; agent payment activity is monitored through AgentCore Observability. Source ↗