Breaking

AWS makes AgentCore payments generally available, with OpenClaw plugin for bounded agent spend

September 3, 2026 at 11:56 EDT

AI Agents
Finance

Amazon Web Services has generally available Amazon Bedrock AgentCore payments, a managed layer that lets AI agents discover, access, and pay for paid APIs, MCP servers, and web content under infrastructure-enforced spending limits. OpenClaw agents can use the aws-agents-pay plugin (@aws/aws-agents-pay on ClawHub) to initiate those payments only after a human provisions a wallet, session, recipients, and budget.

August 18, 2026 · Amazon Bedrock AgentCore

Agents can pay — only inside a human-set budget

AgentCore payments is generally available. OpenClaw’s aws-agents-pay plugin lets agents settle paywalled APIs, MCP servers, and web content after an operator approves the wallet, recipients, and session cap.

Payment loop

1 · Human setupWallet, session, approve

→

2 · HTTP 402Paid URL / MCP

→

3 · ProcessPaymentPolicy + wallet sign

→

4 · ReplayContent within 10 KiB

Model-visible OpenClaw tools

0.001

USDC demo on Base Sepolia

10 KiB

Paid body cap if returned

2.2M

Travala properties on MCP

Per-payment scale (USDC)

Walkthrough demo of 0.001 USDC versus an example ceiling of 0.10 USDC (100×).

0.001

Demo pay

0.10

Example max

What operators like

Spend is bounded by IAM, allowlisted recipients, per-payment and session caps, and expiry — not by a prompt. Runtime cannot mint a new session.

What still applies

The design does not stop prompt injection. Paid bodies are untrusted; concurrent retries can race; samples default to testnet USDC.

Hard split

Humans hold wallet credentials and session write. The agent only calls status and get_paid_content.

Continue reading

The rest of this article is for AI News Blitz readers. Choose an option below to keep reading.