pay.sh Review (2026): Pricing, Features & Honest Verdict
TLDR
pay.sh is a pay-per-call API gateway built by the Solana Foundation in collaboration with Google Cloud that lets AI agents and command-line tools access paid APIs without creating accounts, signing up, or holding API keys. pay.sh is one of the more concrete deployments of the machine-native payments thesis: agents that call APIs without humans in the loop, paying per call in stablecoins, with no account or API key management. Best for: AI agent developers and CLI tool builders who want autonomous, account-free, pay-as-you-go access to paid APIs via stablecoin micropayments. Price: From $0.001 per API call. Rating: 7.6/10.
What is pay.sh?
pay.sh is a pay-per-call API gateway built by the Solana Foundation in collaboration with Google Cloud that lets AI agents and command-line tools access paid APIs without creating accounts, signing up, or holding API keys. Agents pay fractions of a cent per request directly from a crypto wallet using stablecoins on Solana, with pricing exposed at discovery time rather than buried in subscription tiers. The platform supports the x402 protocol (originally incubated by Coinbase, now stewarded by the Linux Foundation) and the Machine Payments Protocol developed by Tempo and Stripe.
pay.sh is designed for the world where AI agents call APIs autonomously without a human intervening to sign up for subscriptions or manage credentials. Providers list APIs in the pay.sh registry where they can be discovered by MCP-compatible agents or CLI tools, and consumers pay only for actual usage. The catalog at launch spans Google Cloud services like Gemini, BigQuery, and Vertex AI, blockchain infrastructure providers like Helius and Alchemy, data services like Dune Analytics and Nansen, and dozens of independent providers.
What Are pay.sh’s Key Features?
Account-Free API Access
Agents and CLI tools can call any API listed on pay.sh without creating an account, signing up, or holding an API key. The wallet replaces the account, and per-request payments replace the API key. This unlocks long-tail API consumption for autonomous agents that cannot realistically register and manage hundreds of separate credentials.
Per-Call Stablecoin Payment
Each API request is paid for individually with stablecoins on Solana, with prices typically in fractions of a cent (for example, CoinStats market data routes at $0.001 per call). When the API returns HTTP 402, pay detects the payment protocol, prepares the transaction, has the local wallet sign it, and retries with the payment proof attached. Settlement is fast enough not to add meaningful latency.
x402 and MPP Protocol Support
pay.sh handles both x402 (incubated by Coinbase, now Linux Foundation) and the Machine Payments Protocol (developed by Tempo and Stripe) so providers can choose either standard. This decouples the gateway from a single payment protocol and makes pay.sh part of the broader machine-native payments ecosystem rather than a proprietary silo.
MCP Server Integration
Compatible with the Model Context Protocol, pay.sh can be exposed as an MCP server so AI agents using Claude Code, OpenAI Codex, OpenClaw, Hermes, or other MCP-aware runtimes can discover and call paid APIs natively. This makes the experience for an agent indistinguishable from calling free tools, except a tiny payment flows on each call.
Provider Catalog and Discovery
The pay.sh registry exposes a catalog of available APIs across categories like AI models, data, blockchain infrastructure, e-commerce, and communications. Agents can fetch the catalog and pick endpoints that match their needs, while providers gain distribution to a new audience of autonomous agents. At launch, the catalog included 50+ Google Cloud and community APIs and is growing.
CLI Access via curl/fetch/wget
Beyond AI agent integration, pay.sh exposes catalog URLs that work with standard tools like curl, fetch, and wget. This gives developers a low-friction way to test endpoints and build automations from the command line without needing to wire up an MCP runtime first. It also makes the platform usable from existing scripts and CI/CD pipelines.
pay.sh Pricing
| Plan | Price | Includes | Best For |
|---|---|---|---|
| Per-call (consumer) | Varies | Pay only for individual API calls in stablecoins on Solana, no account needed | AI agents and CLI tools calling paid APIs |
| Provider listing | Custom | Publish APIs in the registry, set per-call price, receive payments via Solana | API providers monetizing through machine-native payments |
pay.sh is a pay-per-call gateway with no platform subscription. Prices are set by individual API providers and typically fall in the $0.001-$1 range, with examples including QuickNode at $0.001-$1.00, fal.ai at $0.01-$0.07, AgentMail up to $10, dTelecom free, and various Alibaba Cloud services at $0.001. There are no monthly fees for either consumers or providers; revenue flows per request through Solana stablecoin settlement.
Pros and Cons
Pros
- Removes one of the biggest friction points for AI agents calling paid APIs: no signup, no API key management, no subscription minimums.
- Backed by the Solana Foundation in collaboration with Google Cloud, with first-class catalog coverage of Gemini, BigQuery, Vertex AI, and other GCP services.
- Supports both x402 and MPP, the two leading machine-native payment protocols, so it is not locked into a single ecosystem standard.
- Per-call pricing in fractions of a cent is genuinely accessible for high-volume agent workloads where subscription minimums would not work.
- MCP server integration means modern AI agent runtimes can discover and call paid APIs natively without bespoke connector code.
Cons
- Requires a Solana-compatible crypto wallet and stablecoin balance, which is a significant onboarding step for non-crypto-native developers.
- Pricing depends entirely on individual provider settings, so consumers cannot compare costs against a fixed platform tier.
- Newer protocol (x402 launched in 2026) means the long-term standard could shift as competitors like Stripe and Coinbase mature their own offerings.
- Catalog is still relatively small (around 50-72 providers at launch) compared to traditional API marketplaces with thousands of listings.
- Settlement on Solana means agents are exposed to network reliability, gas fluctuations (small but nonzero), and any geographic or regulatory constraints around stablecoin use.
| Plan | Price | Plan Features | Best For |
|---|---|---|---|
| Per-call (consumer) | Varies | Pay only for individual API calls in stablecoins on Solana, no account needed | AI agents and CLI tools calling paid APIs |
| Provider listing | Custom | Publish APIs in the registry, set per-call price, receive payments via Solana | API providers monetizing through machine-native payments |
Who is pay.sh Best For?
Use pay.sh if: AI agent developers and CLI tool builders who want autonomous, account-free, pay-as-you-go access to paid APIs via stablecoin micropayments.
Skip pay.sh if: you need a battle-tested tool with a large community.
Best pay.sh Alternatives
| Tool | What It Does | Price |
|---|---|---|
| RapidAPI | A traditional API marketplace with thousands of APIs, subscription billing, and developer-facing tooling, but built around human signups rather than agent-native payments. | Free tier, paid plans set by API providers |
| Stripe Machine Payments / MPP | The Stripe-Tempo Machine Payments Protocol, a fiat-rail alternative to x402 for agent payments, currently emerging as the other major standard in this space. | Stripe standard processing fees |
| x402 with Coinbase | The original x402 protocol implementation supported by Coinbase, focused on the Ethereum and L2 stablecoin ecosystem rather than Solana, conceptually similar to pay.sh. | Per-call pricing set by API providers |
Final Verdict: Is pay.sh Worth It?
pay.sh is one of the more concrete deployments of the machine-native payments thesis: agents that call APIs without humans in the loop, paying per call in stablecoins, with no account or API key management. The combination of Solana Foundation backing, Google Cloud as a first-class provider, and x402 plus MPP protocol support makes it a credible early standard rather than an experimental side project.
Practical adoption depends on how comfortable your team is with crypto wallets and Solana settlement, and on how many APIs you need being available in the catalog. For agent-heavy workflows experimenting with autonomous tool use, pay.sh is genuinely useful today. For traditional SaaS workflows where one developer signs up for an account and gets an API key, pay.sh is overkill.
FAQ
What is pay.sh and who built it?
pay.sh is a pay-per-call API gateway for AI agents and CLI tools, built by the Solana Foundation in collaboration with Google Cloud and announced in May 2026. It uses stablecoins on Solana for settlement and supports the x402 and Machine Payments Protocol standards for machine-native payments.
How does pay.sh work technically?
When an agent calls a paid API, the API returns HTTP 402 with payment requirements. pay.sh detects the payment protocol, prepares a stablecoin transaction on Solana, has the local wallet sign it, and retries the request with the payment proof attached. The whole flow happens in the API client without human intervention.
Do I need a crypto wallet to use pay.sh?
Yes. Both AI agents and CLI users need a Solana-compatible crypto wallet with a stablecoin balance to make payments. This is a meaningful onboarding step for developers not already working with crypto wallets, and a friction point compared to traditional API marketplaces where a credit card and email are sufficient.
How much do API calls on pay.sh cost?
Pricing is set by individual providers and typically falls in the $0.001-$1 range. Examples include QuickNode ($0.001-$1.00), fal.ai ($0.01-$0.07), CoinStats market data routes ($0.001), AgentMail (up to $10), and dTelecom (free). There is no platform subscription, only per-call charges.
Which APIs are available through pay.sh?
The launch catalog includes around 50-72 providers across AI (Gemini, Vertex AI, fal.ai, third-party LLM providers including Claude Code-compatible endpoints), data (BigQuery, Dune Analytics, Nansen), blockchain infrastructure (Helius, Alchemy), and communications (dTelecom, AgentMail). The catalog is growing as more providers join.
Is pay.sh secure for production use?
pay.sh uses standard stablecoin signing flows where the local wallet authorizes each transaction before it is sent. The protocols (x402, MPP) are open standards stewarded by the Linux Foundation and Stripe respectively. Production use still requires the same security practices any crypto wallet workflow needs, including key management and monitoring.
pay.sh Pros & Cons
What We Like
- Removes one of the biggest friction points for AI agents calling paid APIs: no signup, no API key management, no subscription minimums.
- Backed by the Solana Foundation in collaboration with Google Cloud, with first-class catalog coverage of Gemini, BigQuery, Vertex AI, and other GCP services.
- Supports both x402 and MPP, the two leading machine-native payment protocols, so it is not locked into a single ecosystem standard.
- Per-call pricing in fractions of a cent is genuinely accessible for high-volume agent workloads where subscription minimums would not work.
- MCP server integration means modern AI agent runtimes can discover and call paid APIs natively without bespoke connector code.
What Could Be Better
- Requires a Solana-compatible crypto wallet and stablecoin balance, which is a significant onboarding step for non-crypto-native developers.
- Pricing depends entirely on individual provider settings, so consumers cannot compare costs against a fixed platform tier.
- Newer protocol (x402 launched in 2026) means the long-term standard could shift as competitors like Stripe and Coinbase mature their own offerings.
- Catalog is still relatively small (around 50-72 providers at launch) compared to traditional API marketplaces with thousands of listings.
- Settlement on Solana means agents are exposed to network reliability, gas fluctuations (small but nonzero), and any geographic or regulatory constraints around stablecoin use.
pay.sh FAQ
What is pay.sh and who built it?
pay.sh is a pay-per-call API gateway for AI agents and CLI tools, built by the Solana Foundation in collaboration with Google Cloud and announced in May 2026. It uses stablecoins on Solana for settlement and supports the x402 and Machine Payments Protocol standards for machine-native payments.
How does pay.sh work technically?
When an agent calls a paid API, the API returns HTTP 402 with payment requirements. pay.sh detects the payment protocol, prepares a stablecoin transaction on Solana, has the local wallet sign it, and retries the request with the payment proof attached. The whole flow happens in the API client without human intervention.
Do I need a crypto wallet to use pay.sh?
Yes. Both AI agents and CLI users need a Solana-compatible crypto wallet with a stablecoin balance to make payments. This is a meaningful onboarding step for developers not already working with crypto wallets, and a friction point compared to traditional API marketplaces where a credit card and email are sufficient.
How much do API calls on pay.sh cost?
Pricing is set by individual providers and typically falls in the $0.001-$1 range. Examples include QuickNode ($0.001-$1.00), fal.ai ($0.01-$0.07), CoinStats market data routes ($0.001), AgentMail (up to $10), and dTelecom (free). There is no platform subscription, only per-call charges.
Which APIs are available through pay.sh?
The launch catalog includes around 50-72 providers across AI (Gemini, Vertex AI, fal.ai, third-party LLM providers including Claude Code-compatible endpoints), data (BigQuery, Dune Analytics, Nansen), blockchain infrastructure (Helius, Alchemy), and communications (dTelecom, AgentMail). The catalog is growing as more providers join.
Is pay.sh secure for production use?
pay.sh uses standard stablecoin signing flows where the local wallet authorizes each transaction before it is sent. The protocols (x402, MPP) are open standards stewarded by the Linux Foundation and Stripe respectively. Production use still requires the same security practices any crypto wallet workflow needs, including key management and monitoring.
