Ensure your Amazon Bedrock agent is deployed in a supported region (US East N. Virginia, US West Oregon, EU Frankfurt, or AP Sydney); AgentCore Payments entered preview on May 7, 2026 in these four regions.
In the Bedrock AgentCore console, navigate to Payments and add a payment connection: choose either a Coinbase CDP wallet (for on-chain USDC x402 payments) or a Stripe Privy wallet (for fiat or Stripe MPP payments).
Set session-level spending limits — a maximum total spend per agent session — and optionally per-request limits; AgentCore enforces these as guardrails before authorizing any payment.
In your agent definition, grant the payments capability; the agent can now call the built-in pay_for_resource tool, which handles the full x402 402→payment→retry cycle automatically.
After deployment, review the payment audit trail in CloudWatch Logs and the AgentCore Payments dashboard; every transaction is logged with timestamp, resource URL, amount, and settlement status.
Known gotchas
AgentCore Payments is in preview as of June 2026; AWS may change pricing, API shapes, or regional availability before general availability — pin your SDK version and monitor the AWS what's-new feed.
Session spending limits are enforced per agent invocation session, not per calendar period; a long-running agent session could exhaust limits quickly if it calls many paid services — set conservative limits and handle the limit-exceeded error gracefully.
Coinbase CDP wallet connections require a funded Base mainnet wallet; Stripe Privy wallet connections require a Stripe account in good standing — both must be configured before the agent can transact.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp