x402 payments now ship natively inside AWS. AgentCore payments hit general availability today, meaning any agent built on Bedrock can pay for APIs, data, and model inference on its own, with spending caps enforced by the infrastructure. ampersend has been running this in production since the preview. an agent sends a request to a paid model endpoint, receives a payment required response, pays in USDC on Base, and gets its answer back. one integration covers every provider, and ampersend settles with them behind the scenes. AWS published the full walkthrough of our build: aws.amazon.com/blogs/machine…

compliance screening is live in ampersend. agents paying for APIs and services over x402 move funds autonomously, and teams operating in regulated environments need those payments checked against sanctions and risk data before money moves. ampersend now handles that natively. once enabled, every x402 payment runs through @trmlabs screening before settlement. the counterparty wallet gets checked against TRM's risk intelligence, covering sanctioned entities and flagged addresses, and settlement only proceeds on a clean result. flagged payments stop before funds leave the wallet. screening happens inline, without a separate review queue slowing settlement. it's opt-in, configured per account, and runs within the payment flow, so agents keep their speed while every transaction stays within policy. watch @rodventures explain ⬇️

ampersend built a pay-per-intelligence routing layer on Amazon Bedrock AgentCore Payments, and @awscloud published the full technical breakdown this week. the core problem: every agent that needs to call a paid model, a paid data API, or a paid content endpoint has to build the same infrastructure from scratch. wallet management, payment signing, x402 protocol implementation, spend limits, and a billing integration for every provider it wants to reach. that's months of engineering before a single line of agent logic ships. ampersend sits between the agent and a marketplace of model providers. the agent calls ampersend, picks a model tier matched to the task complexity, and pays per request. ampersend selects the upstream provider, routes the request, and settles with that provider onchain. from the agent's perspective, it made one paid request to one endpoint. everything behind that is abstracted away. Amazon Bedrock AgentCore Payments handles the infrastructure that makes autonomous transactions safe. it connects to Coinbase CDP for wallet custody and signing, so the agent never touches a private key. session-level spend budgets are enforced at the infrastructure layer, set by the application backend, with hard limits the agent cannot override. when an endpoint returns an HTTP 402, AgentCore handles the full x402 negotiation, signs the USDC payment, and delivers the proof, without interrupting the agent's reasoning loop. every transaction flows through the same logs and traces developers already use in AgentCore. the payment pattern is two hops. agent pays ampersend through AgentCore. ampersend pays the upstream model provider, in this case BlockRun, using the ampersend SDK, settling in USDC on Base. one integration for the agent builder, full provider flexibility behind it. the full integration shipped in under two weeks. AWS estimated that building equivalent wallet custody, signing infrastructure, and spend controls from scratch would have taken 3-4 months of engineering. that delta is the point: agentic commerce needs managed infrastructure the same way web apps need managed auth. the plumbing shouldn't be the hard part.

ampersend is featured on the @awscloud machine learning blog today. we built a pay-per-intelligence routing layer on top of Amazon Bedrock AgentCore Payments. agents autonomously select a model tier, pay per request in USDC on Base, and stay within governed spend limits throughout. AgentCore handles wallet custody, payment signing, and session-level budgets at the infrastructure layer. the two-hop pattern: agent pays ampersend via x402 through AgentCore, ampersend settles with the upstream model provider. from the agent's perspective, it made one request to one endpoint. routing, payment, and provider selection all happen transparently in between. the full integration took under two weeks. the AWS team estimates equivalent wallet custody and signing infrastructure would have taken 3–4 months of engineering without AgentCore Payments. read the full breakdown on the AWS ML blog 👇

🚨We're going live today with @chainlink and @trmlabs: a free workshop on autonomous agent payments, covering the risk, the threat surface, the proof layer, and the controls. Live at 4PM UTC on X or YouTube. 🔗 luma.com/1xu0jgc3

Tomorrow we sit down with @chainlink and @trmlabs to talk governance for AI agents that transact on their own. Forward this to whoever owns compliance at your company, because the hour covers exactly what they keep asking about: enterprise exposure, the agentic threat landscape, cryptographic proof of execution, and controls that hold up in an audit. 🎤 Free webinar on agent payment governance 🗓️ June 18, 4PM UTC 📍 Live on X and YouTube 🔗 RSVP: luma.com/1xu0jgc3

Closing out the lineup for our June 18 webinar on compliance for autonomous agent transactions: Alex Kopferschmitt, strategic partnerships at @trmlabs. Alex works with financial institutions and public sector teams on turning blockchain intelligence into working defense against illicit finance, with a decade across cybersecurity and enterprise tech behind him. Live on the webinar, he will map the agentic threat surface: the attack vectors and compliance failures that emerge once agents transact on their own. 🎤 Free webinar on agent payment governance 🗓️ June 18, 4PM UTC 📍 Live on X and YouTube 🔗 RSVP: luma.com/1xu0jgc3