surface
No-payment route map
Manifest, OpenAPI, direct endpoint, 402 challenge, MPP header, browser preflight, and resource-binding notes.
agent payment launch review / may 2026
AWS AgentCore Payments, Cloudflare Workers, x402, MPP, and Pay.sh are making paid API calls part of the agent runtime. This page turns a launch surface into a concrete review scope: no-payment 402 checks, spend-map controls, cache policy, CORS, replay/idempotency, metadata filtering, receipt evidence, and a patch order.
deliverable
surface
Manifest, OpenAPI, direct endpoint, 402 challenge, MPP header, browser preflight, and resource-binding notes.
spend
Session cap, per-call cap, recipient allowlist, wallet isolation, approval gates, and denial paths.
http
Checks for browser-readable payment challenges, `X-PAYMENT` preflight, `Cache-Control`, `Vary`, and paid-response cache hazards.
settle
Request ids, idempotency, facilitator binding, finality assumptions, failed-payment reconciliation, and receipt proof.
privacy
Prompt text, query tokens, user identifiers, resource URLs, and receipt fields are reviewed for unnecessary leakage.
order
The output is ranked by launch risk, so the first fix is the one most likely to block trust or break a real buyer flow.
source ledger
aws
AWS describes payment connections through Coinbase and Stripe/Privy wallets, session-level spending limits, and automatic x402 handling when agents hit paid resources.
open AWS notecloudflare
Cloudflare documents agentic payments through HTTP 402, including x402 and MPP paths for Workers and MCP tools.
open Cloudflare docsresearch
The May 2026 x402 attack preprint maps practical risks around finality, settlement binding, replay, HTTP cache/proxy behavior, and discovery selection.
open arXiv papertooling
`x402-surface-check@0.2.22` adds optional strict cache findings for teams that want missing payment-challenge cache policy called out before launch.
open surface checkerPrivate-first review