cap
Loss is bounded before execution.
Session and per-call ceilings should be enforced outside the prompt so a model cannot talk its way into more spend.
agentcore payment policy / may 2026 signal
AgentCore Payments, x402, MPP, and Pay.sh move paid APIs into an agent's execution loop. This local builder turns a payment demo into concrete session caps, per-call limits, recipient allowlists, approval gates, receipt rules, metadata boundaries, and audit evidence.
launch posture
cap
Session and per-call ceilings should be enforced outside the prompt so a model cannot talk its way into more spend.
payee
New payees, changed networks, large amounts, and unknown facilitators should deny or pause until a human confirms.
memo
Payment records should carry compact purpose codes, not full prompts, support tickets, emails, or hidden query strings.
audit
Receipts, denials, retries, traces, and refunds should explain what happened without exposing private user context.
source ledger
aws
AWS announced AgentCore Payments preview on May 7, 2026 with Coinbase and Stripe, including session spending limits, observability, x402 negotiation, and paid MCP/API access.
open AWS notedocs
The AgentCore docs describe payment sessions with configurable payment limits, expiry, instruments, and payment lifecycle orchestration.
open docscloudflare
Cloudflare's Agents docs frame x402 and MPP as protocols for agents purchasing resources through HTTP 402 payment flows.
open docsquicknode
Quicknode documents x402 and MPP as wallet-based protocols for applications and agents accessing blockchain infrastructure.
open docs