AWS and the OpenClaw Foundation have introduced a method for autonomous agents to make payments through Amazon Bedrock AgentCore. This allows agents to access services that require HTTP 402 Payment Required responses without human intervention. The solution includes wallet integration, spending limits, and a consistent payment layer as agent payment protocols evolve. The integration supports protocols such as x402 and Machine Payments Protocol (MPP), enabling programmatic payment flows between agents and services. This approach ensures that agents can continue operations within predefined budget and expiry limits set by human administrators. The system is designed to handle small transactions, often less than one dollar, using stablecoin payments for near-real-time settlement. This makes HTTP-native protocols like x402 suitable for agent-initiated payments. Implementing this directly requires wallet-provider integration, protected credential handling, and payment observability. The design assumes untrusted input can manipulate the model, but it bounds the runtime’s authority by recipient, asset, network, per-payment amount, session budget, and expiry. The solution separates human-run payment administration from the model-facing runtime. A human provisions the wallet, creates the payment session, approves recipients, and sets the budget in a trusted terminal. The aws-agents-pay plugin exposes two model-visible tools: get_payment_session_status and get_paid_content. The runtime can initiate a payment within the approved session but cannot create, extend, or replace a session. The process involves confirming the session, requesting an approved URL, validating the network, asset, recipient, and amount against the operator’s policy, and then calling ProcessPayment. For retries, the plugin reuses the same idempotency token rather than creating a second payment. The plugin waits until the signed authorization’s validAfter time, then replays the original request with the payment signature. With returnBody enabled, the plugin returns the paid response body, caps it at 10 KiB, and marks it as untrusted: true. The current OpenClaw setup flow in the Agent Toolkit for AWS provides an example for Base Sepolia for testing and Base for production, and supports customization for other chains, including Ethereum, other EVM-compatible chains, and Solana. The collaboration includes support for community events like ClawCon and direct engineering work with the OpenClaw Foundation’s team to bring AgentCore payments into the plugin framework. The integration enables agents to have a production-grade path to pay for what they use while maintaining the same conversational setup as other OpenClaw plugins. The implementation steps involve configuring OpenClaw to make bounded payments, including prerequisites like OpenClaw version 2026.3.24 or later, Node.js and npm, an AWS account with access to AgentCore payments, and separate IAM roles for administration and runtime. Coinbase CDP or Stripe with Privy credentials, entered only in the interactive AgentCore CLI, are also required. A Base Sepolia x402 v2 endpoint that you control or have independently approved is needed. You can use the Coinbase x402 Bazaar to discover candidate services, but verify the endpoint, recipient, network, asset, and price before adding them to the payment policy.

AWS and the OpenClaw Foundation have collaborated on this integration, including support for community events like ClawCon and direct engineering work with the Foundation’s team to bring AgentCore payments into the plugin framework. The integration enables agents to have a production-grade path to pay for what they use while maintaining the same conversational setup as other OpenClaw plugins. The implementation steps involve configuring OpenClaw to make bounded payments, including prerequisites like OpenClaw version 2026.3.24 or later, Node.js and npm, an AWS account with access to AgentCore payments, and separate IAM roles for administration and runtime. Coinbase CDP or Stripe with Privy credentials, entered only in the interactive AgentCore CLI, are also required. A Base Sepolia x402 v2 endpoint that you control or have independently approved is needed. You can use the Coinbase x402 Bazaar to discover candidate services, but verify the endpoint, recipient, network, asset, and price before adding them to the payment policy.

The collaboration between AWS and the OpenClaw Foundation includes support for community events like ClawCon and direct engineering work with the Foundation’s team to bring AgentCore payments into the plugin framework. The integration enables agents to have a production-grade path to pay for what they use while maintaining the same conversational setup as other OpenClaw plugins. The implementation steps involve configuring OpenClaw to make bounded payments, including prerequisites like OpenClaw version 2026.3.24 or later, Node.js and npm, an AWS account with access to AgentCore payments, and separate IAM roles for administration and runtime. Coinbase CDP or Stripe with Privy credentials, entered only in the interactive AgentCore CLI, are also required. A Base Sepolia x402 v2 endpoint that you control or have independently approved is needed. You can use the Coinbase x402 Bazaar to discover candidate services, but verify the endpoint, recipient, network, asset, and price before adding them to the payment policy.

Source: awsml