pay.sh is committed to bridging the gap between AI agents and paid APIs.

Written by: KarenZ, Foresight News

An agent that can write code, search for information, and call tools by itself often gets stuck at the most rudimentary step: payment.

What pay.sh aims to dismantle is this wall. On May 5th, the Solana Foundation collaborated with Google Cloud to launch pay.sh. This product does not create a consumer-facing wallet nor does it attempt to build a payment button. Instead, it focuses on another type of more specific demand: when agents need to call paid APIs, they won’t need to register manually or use API Keys; instead, they can pay as needed to complete the payment and gain access for the call.

Simply put, what pay.sh aims to solve is trying to break down the action of "calling an API" into a more machine-friendly process: seeing the price, initiating the request, authorizing the payment, and getting the result.

According to information from the Solana Foundation and the pay.sh official website, the first batch of integrated APIs already covers some of Google Cloud’s APIs, including Gemini, BigQuery, Vertex AI, BigTable, Cloud Run, and more than 50 community API facilitators offering services in e-commerce, data, communication, and on-chain infrastructure.

What exactly is Pay.sh?

From the official description, pay.sh is a coordination layer for proxy payments and calls aimed at paid APIs. It wraps the command-line tools and agent workflows that developers are familiar with, and when the target API presents a challenge of “paying first before receiving data,” pay will recognize the payment protocol, prepare the payment credential, request wallet authorization locally, and then retry the request once completed. For developers, that previously error-prone curl request only had an additional 'pay' added in front; for agents, they receive a tool path that can directly utilize payment capabilities.

There are several key points here.

• What payment protocol to use? Technologically, pay.sh bets on open machine payment standards. The official mentions that pay.sh is built on the x402 and MPP payment protocols.
• Payment method: The underlying payment settlement of pay.sh relies on stablecoins on Solana. The Solana Foundation notes that users can complete funding with credit cards or stablecoins in about 60 seconds.
• Signature: pay.sh doesn’t allow agents to "run free" with private keys. According to the official website and GitHub README, its local authorization process utilizes system-level security capabilities, such as macOS's Keychain and Touch ID, Windows Hello, GNOME Keyring, or 1Password. This means that initiating a call by the agent can be automated, but real signing for release can still retain a controllable authorization step at the lower layer. This design is akin to providing AI agents with a "controlled credit limit, visible actions" payment card rather than throwing the company's safe key to it.

Who are the initial partners?

When any infrastructure project is launched, the easiest page to overlook is often the list of partners.

The initial launch partners for pay.sh community-source endpoints include: PayAI, Crossmint, Merit Systems, Corbits, MoonPay, Sponge Wallet, ATXP, Tektonic Company.

MoonPay and Crossmint complement the funding entry and wallet infrastructure. The former resolves the conversion between fiat currency and stablecoins, while the latter provides enterprise-level wallets, stablecoins, and payment integration. Without this layer, agent payments can only get stuck within the small 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 agent trading protocol layer, involving agent identity, task collaboration, and payment flow.

As for Merit Systems, Corbits, PayAI, and Tektonic Company, they are not just payment plugins but more like service providers and aggregation layers of the agent economy, helping service providers integrate APIs, data, and payment capabilities into this system. Merit Systems has already provided various stablecoin-priced data, media, communication, and upload APIs in the pay.sh directory.

In other words, pay.sh is not just looking to solve "how to pay," but aims to connect the entire chain of "how agents discover services, how they obtain quotes, how they complete authorization, and how they settle instantly" together, more like a coordination layer that consolidates already existing capabilities scattered among different facilitators and service providers into a unified directory, giving agents and developers a unified entry point.

If Google Cloud provides the top-level enterprise API entry and infrastructure backing, then community partners provide breadth and long-tail supply.

In the future, consumers may be layers of agents representing humans executing tasks. As long as this transformation truly occurs, the billing methods and distribution logic of the API market must change accordingly.