AI agents are no longer just being trained to find information and call tools. The latest cloud experiments are giving them a way to pay for what they use.

AWS and Google Cloud have both moved in the same direction within days of each other: letting AI agents access digital services through stablecoin payment rails. That may sound like a crypto side quest, but the bigger story is more practical. If an agent can discover an API, accept a price, pay a tiny amount, and keep working without a human opening an account or entering a card, software starts to look less like a workflow and more like an economic actor.

The AWS product is Amazon Bedrock AgentCore Payments, announced in preview on May 7. It is built with Coinbase and Stripe, and it lets developers connect a Coinbase CDP wallet or a Stripe Privy wallet so an agent can pay for APIs, MCP servers, web content, and other agents while it is running. The mechanism is built around HTTP 402 and x402, the payment protocol Coinbase has been pushing for machine-native commerce. When an agent hits a paid resource, AgentCore can handle the payment negotiation, wallet authentication, transaction execution, and proof delivery without breaking the agent’s reasoning loop.

Google Cloud’s move came through Pay.sh, introduced by the Solana Foundation in collaboration with Google Cloud on May 5. Pay.sh is a gateway rather than a standard Google Cloud billing product. It sits in front of services such as Gemini, BigQuery, Vertex AI, Cloud Run, and community APIs, letting agents pay per request using stablecoins on Solana. The agent’s Solana wallet becomes both identity and payment instrument. No conventional API key. No subscription plan. No billing account created for every service an agent might need.

That is the real shift. Agents have been sold as autonomous workers, but most of the internet still assumes a human buyer sits somewhere in the loop. A person creates the SaaS account. A finance team approves the spend. A developer stores the API key. A billing admin reconciles the invoice. That model works for companies and users, but it is clumsy for agents that may need to call dozens of tools during a single task.

Stablecoins fit the agent story because they are programmable, global, and small-denomination by design. In the AWS model, the agent can pay for resources through connected Coinbase or Stripe wallet infrastructure. In the Google Cloud and Solana model, the agent can draw down from a Solana wallet on a per-request basis. The early supported rails point toward USDC and other dollar stablecoins, though the important detail is not the brand of coin. It is the idea that payment can happen at the same speed and granularity as an API call.

As the Solana Foundation’s launch note described it, Pay.sh is designed to make the payment itself act like the credential. That is a clean concept for developers. Instead of managing account creation, API keys, minimum spend commitments, and recurring invoices, an agent can see a price, pay it, and receive access. For startups building agent products, that could reduce one of the least glamorous but most persistent integration problems: how to let autonomous software consume paid services without turning every workflow into a procurement exercise.

AWS is taking a more cloud-native route. AgentCore Payments is available only in preview across selected regions, including Northern Virginia, Oregon, Frankfurt, and Sydney. That matters because this is not yet a fully mature, broadly available payment layer for all AI commerce. It is a developer tool with guardrails, observability, and spending limits built into the infrastructure. Session-level budgets are a key part of the product, because nobody wants an agent that can reason well but spend badly.

The risk moves from capability to control

The obvious concern is not whether an agent can send a payment. The concern is who is responsible when it sends the wrong one. If an AI agent buys access to a fraudulent API, overpays for a low-value service, or gets manipulated into draining its budget through prompt injection, the liability will not be theoretical. It will land on developers, cloud platforms, wallet providers, enterprise customers, or some mix of all four.

That is why custody and policy controls matter as much as the payment protocol. AWS is leaning on Coinbase and Stripe wallet connections, with infrastructure-level spending governance and logs. Pay.sh uses a Solana wallet and a gateway that applies rate limits, quotas, and access controls before routing requests to cloud and community services. Anchorage Digital’s separate Agentic Banking launch with Google Cloud this week shows the institutional version of the same problem: enterprises want agents to access capital, but only through identity, compliance checks, audit trails, and policy enforcement.

There is also a compliance question that stablecoins do not magically solve. Know Your Customer rules, sanctions screening, fraud monitoring, chargeback expectations, tax reporting, and consumer protection were built around humans and companies. Agentic payments will force regulators and infrastructure providers to define what it means for a machine to be authorized, identified, monitored, and stopped. The phrase Know Your Agent may sound neat, but it will need real operational teeth.

For founders, the near-term opportunity is clearer than the regulatory roadmap. Any startup offering data, models, verification, scraping, security checks, compute, or specialist APIs can start thinking about agent-readable pricing and pay-per-use access. If agents become buyers, services will need storefronts built for software, not humans. That means machine-readable descriptions, transparent pricing, fast settlement, reliable dispute handling, and limits that customers can actually understand.

The market should treat this week as an early infrastructure signal, not a finished revolution. AWS is in preview. Pay.sh is a gateway experiment tied to Solana’s payment stack. Enterprise adoption will depend on security, trust, accounting, and whether developers find the experience simpler than existing billing. Still, the direction is hard to miss. AI agents are getting wallets because the next phase of automation is not just about deciding what to do. It is about being able to pay for doing it.

Also read: A Michigan data center fight shows AI infrastructure is outgrowing local vetoes • Nvidia is turning AI funding into a supply chain weapon • Cloudflare’s AI layoffs turn efficiency into a market test