pay.sh is dedicated to bridging the gap between AI agents and paid APIs.
Article by KarenZ, Foresight News
An agent that can write code, research information, and even call its own tools often gets stuck at the simplest step: making a payment.
What pay.sh aims to dismantle is this wall. On May 5, the Solana Foundation, in collaboration with Google Cloud, launched pay.sh. This product does not target consumer wallets or seek to recreate a payment button. Instead, it addresses a more specific need: when an agent needs to call a paid API, it enables payment on-demand without manual registration or API keys—granting access immediately after payment.
In simple terms, pay.sh aims to break down the act of "calling an API" into a machine-friendly sequence: see the price, initiate a request, authorize payment, and receive the result.
According to information from the Solana Foundation and the pay.sh website, the initial integration scope covers select Google Cloud APIs, including Gemini, BigQuery, Vertex AI, BigTable, and Cloud Run, as well as over 50 community API facilitators offering services in e-commerce, data, communications, and on-chain infrastructure.
What exactly is Pay.sh?
According to its official description, pay.sh is a proxy payment and invocation coordination layer designed for paid APIs. It wraps familiar command-line tools and proxy workflows, automatically detecting payment protocols when a target API presents a "pay first, then receive data" challenge. pay prepares payment credentials, prompts local wallet authorization, and retries the request upon successful payment. For developers, the only change to their previously failing curl command is adding "pay" at the beginning; for proxies, it provides a direct tool path capable of consuming paid services.
Here are several points that are particularly important.
- What payment protocols are used? Technically, pay.sh is built on open machine payment standards. The official documentation explicitly states that pay.sh is based on the x402 and MPP payment protocols.
- Payment Method: Pay.sh's underlying payment settlement relies on stablecoins on Solana. The Solana Foundation notes that users can complete deposits via credit card or stablecoin in approximately 60 seconds.
- Signature: pay.sh does not require the agent to directly access the private key in plain text. According to the official website and GitHub README, its local authorization process leverages system-level security features such as macOS Keychain and Touch ID, Windows Hello, GNOME Keyring, or 1Password. This means that while agent-initiated requests can be automated, the underlying signing process still retains a controlled authorization step. This design is akin to giving an AI agent a payment card with limited spending authority and visible transaction activity—rather than handing over the keys to the company safe.
Who else is launching as a partner?
When any infrastructure project is first launched, the page most often overlooked is the list of partners.
Launch partners for the pay.sh community source endpoint include: PayAI, Crossmint, Merit Systems, Corbits, MoonPay, Sponge Wallet, ATXP, and Tektonic Company.
MoonPay and Crossmint fill the gap in payment entry points and wallet infrastructure. MoonPay enables conversion between fiat currency and stablecoins, while Crossmint provides enterprise-grade wallet, stablecoin, and payment integrations. Without this layer, agent-based payments would remain confined to the narrow circle of on-chain native users.
Sponge Wallet is closer to the role of an agent wallet and payment gateway, wrapping third-party APIs into directly callable, pay-per-use interfaces; ATXP emphasizes the layer of代理交易协议, involving agent identity, task collaboration, and payment flow.
Regarding Merit Systems, Corbits, PayAI, and Tektonic Company, they are not merely payment plugins but rather service providers and aggregation layers within the agent economy, helping service providers integrate their APIs, data, and payment capabilities into this ecosystem. Merit Systems already offers a variety of APIs for data, media, communication, and uploads, all priced in stablecoins, within the pay.sh directory.
In other words, pay.sh isn’t just about solving “how to pay”—it aims to connect the entire workflow: how agents discover services, obtain quotes, complete authorization, and settle payments in real time. It acts more like a coordination layer, consolidating capabilities that already exist but are scattered across different facilitators and service providers into a single unified directory, offering agents and developers a unified entry point.
If Google Cloud provides top-tier enterprise API access and infrastructure backing, then community partners offer breadth and long-tail supply.
In the future, consumers may consist of layers of agents acting on behalf of humans. If this shift truly occurs, the billing models and distribution logic of the API market must adapt accordingly.