Solana and Google Cloud Launch Pay.sh — AI Agents Now Pay Per API Call With Stablecoins

The Solana Foundation and Google Cloud launched Pay.sh on May 5, a stablecoin payment gateway purpose-built for AI agents operating autonomously across the web. The service allows an AI agent to discover available APIs, receive live rate quotes, and pay per individual request from a Solana wallet — with no account registration, no monthly invoicing, and no human operator required to authorize each transaction. Settlement happens in stablecoins on Solana after provider reconciliation, using two open standards co-developed by the broader industry: x402, which embeds payment authorization into HTTP request headers, and MPP (Machine Payment Protocol), which handles agent-to-API commerce semantics.

What APIs Are Available and How the Payment Flow Works

Pay.sh launches with support for a set of Google Cloud's most widely used AI and data APIs: Gemini (inference), BigQuery (data warehousing), BigTable (NoSQL storage), Cloud Run (serverless execution), and Vertex AI (ML platform). Beyond Google Cloud's own catalog, the platform opens with more than 50 community API facilitators spanning e-commerce, market data, communications infrastructure, and blockchain data. The result is a marketplace where an agent can provision access to both cloud-native compute and specialized third-party data — such as real-time DEX pricing or on-chain analytics — from a single wallet identity.

The payment flow is deliberately minimal. An agent's Solana wallet address functions as its identity; it doesn't need to create an account or pass a KYC process. When the agent issues an API request, x402 encodes a payment authorization into the HTTP header, which the endpoint verifies against a Solana stablecoin balance before responding. Access controls — rate limits, quotas, tier restrictions — are enforced at the endpoint rather than in a central billing system. Providers receive funds after reconciliation, not in real time per request, which gives providers flexibility to batch settlements on their preferred cadence.

The architecture eliminates the primary friction point in current API economics for autonomous agents: the requirement that a human operator maintain a billing relationship with each provider. An agent running an unattended research or trading workflow today must either be pre-authorized against a shared API key (introducing security and attribution complexity) or trigger human intervention for each new provider. Pay.sh makes the agent itself the principal in the billing relationship.

x402: The Open Standard Making This Possible

Pay.sh is built on x402, an open payment protocol co-created by Coinbase and Cloudflare in 2025. x402 repurposes the dormant HTTP 402 "Payment Required" status code — which has existed in the HTTP specification since 1992 but was never standardized — as a machine-native payment handshake. When a server returns a 402 response with an x402 header, the client (in this case an AI agent) knows the resource costs a specific amount in USDC, executes the on-chain payment, and re-issues the request with a payment receipt. The entire exchange adds one round-trip to the request latency.

The x402 Foundation, which governs the standard, includes Coinbase, Cloudflare, Google, and Visa. As of March 2026, x402 had processed over 119 million transactions on Base and 35 million on Solana, handling roughly $600 million in annualized volume at zero protocol fees. The Solana Foundation's decision to build Pay.sh on x402 rather than a proprietary standard signals a commitment to interoperability: an agent that learns to pay via x402 on Pay.sh can, in principle, use the same payment logic with any x402-compatible endpoint on any chain.

Cloudflare's Chief Strategy Officer noted recently that more than 50% of internet traffic is now non-human, growing at 60% annually for the agent-traffic segment specifically. x402 represents the infrastructure layer's answer to that shift: instead of treating AI agent requests as an anomaly to be blocked or rate-limited, websites and APIs can monetize them directly, at per-request granularity, without human billing overhead.

What to Watch

The key signal to track is transaction volume on Pay.sh in its first 90 days — specifically whether developer-built agents or enterprise-deployed workflows dominate early usage. If developer-built agents are the first movers, the rate of third-party API integrations will be the growth lever; if enterprise workflows move first, the Google Cloud–native APIs will drive volume. Watch also for competing launches from AWS and Azure: neither has announced an equivalent pay-per-request stablecoin gateway, and if Pay.sh gains meaningful developer adoption, competitive pressure to build parity products will mount quickly. Finally, the MPP standard's governance trajectory matters: if MPP becomes an IETF draft or gains W3C recognition, x402-based payments move from crypto-adjacent infrastructure to core internet plumbing — and Solana's position as the settlement layer becomes structurally advantaged.

Want every AI × Web3 signal the moment it breaks? Subscribe to the BlockAI News daily brief.