Invoket

Do managed agent wallets change anything for an API seller?

AWS AgentCore Payments and Fireblocks give agents managed x402 wallets with spend policies — growing the buyer pool for every standard x402 API.

By Matthias Begot · · Updated

For anyone selling a paid API, the answer is short: nothing to integrate, and a larger pool of buyers. In May 2026, two heavyweight infrastructure vendors shipped managed wallets for AI agents — AWS with Amazon Bedrock AgentCore Payments (preview, May 7) and Fireblocks with its Agentic Payments Suite (May 20) — and both speak standard x402. Every platform of this kind enlarges the population of solvent, policy-governed agents that can discover and pay for a standard x402 endpoint, with zero integration work on the seller’s side, provided the seller’s surface is machine-readable.

What AWS shipped: AgentCore Payments

Amazon Bedrock AgentCore is AWS’s managed runtime for production agents. On May 7, 2026, AWS announced AgentCore Payments in preview — described as payment capabilities purpose-built for autonomous agents, “enabling AI agents to autonomously access and pay for APIs, MCP servers, web content, and other agents” (AWS What’s New). The mechanics, per the launch post:

  • Managed wallet connection. The developer connects a Coinbase CDP wallet or a Stripe Privy wallet as a “payment connection”; the agent never handles private keys, and the developer never builds payment plumbing.
  • In-loop x402 negotiation. When the agent hits a paid endpoint and gets an HTTP 402, the runtime “authenticates with the configured wallet, executes the stablecoin payment, attaches payment proof, and delivers the content back to the agent, all within the execution loop” — the agent’s reasoning is never interrupted by the payment.
  • Deterministic spend governance. Spending limits are set per session and “enforced deterministically at the infrastructure layer” — not by prompting the model to be frugal. Every transaction lands in the same logs, metrics and traces developers already use in AgentCore.
  • Discovery included. The Coinbase x402 Bazaar MCP server is available through AgentCore Gateway, exposing “over 10,000 x402 endpoints that agents can search, discover, and pay for autonomously.”

The preview runs in four regions (N. Virginia, Oregon, Frankfurt, Sydney). AWS pairs it with a seller-side story too: CloudFront with Lambda@Edge as an x402 monetization layer, covered in Is anyone actually paying with x402? The mid-2026 record.

What Fireblocks shipped: the Agentic Payments Suite

Fireblocks — the institutional custody vendor — announced its Agentic Payments Suite on May 20, 2026, and joined the x402 Foundation in the same release, contributing a security extension for request integrity and spend governance (press release). The suite covers both sides of a transaction:

  • Agentic Wallets — programmable wallet infrastructure fintechs offer to their end users, who delegate funds to agents within defined spending limits. Agents can “access funds, sign transactions, and pay any merchant accepting x402 or MPP within defined limits, with a full audit trail.”
  • Agentic Payments Gateway — lets payment service providers offer merchants stablecoin acceptance the way they offer card acquiring, with compliance, reconciliation and off-ramp handled by the platform.

Where AWS targets the developer running an agent, Fireblocks targets the fintech or PSP putting wallets in end users’ hands. Different customer, same protocol on the wire.

The pattern: custody and governance move into the platform

Managed wallets answer the two objections that kept serious money away from agent payments:

  1. Key custody. An agent holding a raw private key is an incident report waiting to be written. In both offerings the key lives with a custodian (Coinbase CDP, Privy, Fireblocks), and the agent gets scoped, revocable authority — not the key itself.
  2. Unbounded spend. A model deciding freely how much to pay is not a control; a per-session limit enforced by infrastructure is. Both platforms make the spend policy a deterministic layer outside the model, with an audit trail connecting each payment to the agent run that caused it.

None of this changed the protocol. The wallet platforms differentiate on custody, policy and observability — but on the wire, each of their agents performs the same standard exchange: request, 402 challenge, signed payment, replay.

The seller-side read: don’t integrate — be discoverable

This is the part that matters if you operate a paid API. A seller does not need an AWS partnership, a Fireblocks account, or any platform-specific SDK to be payable by these agents. A standard x402 endpoint is already compatible with all of them, and with the next platform that launches. The leverage is not integration; it is discovery — being findable and legible to agents you have never met:

  • A live catalog. Invoket’s /catalog is the gateway’s own machine-readable price list — endpoints, assets, networks and current prices, always authoritative (this article, per house rule, quotes none of them).
  • A domain manifest. /.well-known/x402.json tells an agent landing on the domain where the gateway and catalog live.
  • An LLM site map. llms.txt gives answer engines and agent frameworks a curated map instead of a crawl.
  • Registry presence. The x402 Bazaar — the same index AgentCore Gateway now serves to Bedrock agents as an MCP server — is where those 10,000+ endpoints come from. Being indexed there puts an endpoint in front of every Bedrock agent with a wallet, with no bilateral contract. How the Bazaar and MCP discovery work is covered in How does an agent find a paid API with no human in the loop?.

All four surfaces are documented in For agents.

The flow, end to end

Concretely, here is what a Bedrock agent with a managed wallet does when its task requires, say, sanctions context on a beneficiary bank:

  1. The agent searches the x402 Bazaar MCP server (via AgentCore Gateway) and finds Invoket’s /iban/screen endpoint.
  2. It calls the endpoint and receives 402 Payment Required with the price, asset and network in the challenge.
  3. AgentCore checks the session’s spend policy, authenticates with the connected wallet, signs the payment, and replays the request with proof attached — inside the execution loop.
  4. The gateway settles and returns the result; the payment appears in the developer’s AgentCore traces, tied to the agent run.

The seller’s server saw an ordinary x402 exchange — the same one any client performs in the Quickstart, and the same loop dissected in What happens between a 402 challenge and the paid response. Nothing in it reveals, or needs to reveal, that a managed platform stood behind the wallet.

Caveats worth keeping in view

  • AgentCore Payments is a preview, in four regions, and preview terms can change before general availability.
  • Fireblocks sells to fintechs and PSPs, not to individual agent developers; its wallets reach agents through those intermediaries, so the ramp is slower than a developer-facing launch.
  • Platform growth is not demand. As the mid-2026 record details, x402 infrastructure has run ahead of organic usage. Managed wallets remove real blockers — custody and spend control — but they create capacity to pay, not reasons to pay. The reasons remain what they always were: endpoints that do useful work per settlement.

The strategic takeaway is symmetric to the technical one. Because every wallet platform speaks the same protocol, sellers should resist building for any single one of them. Keep the endpoint standard, keep the discovery surfaces clean, and every new wallet launch — AWS’s, Fireblocks’, and the next one — becomes distribution you did not have to build.

Sources