# The Week Solana Brought Google to x402

*Author: David Christopher*
*Published: May 9, 2026*
*Source: https://www.bankless.com/de/read/the-week-solana-brought-google-to-x402*

---

This week’s biggest news came from the other side of the fence: Solana. 

The [Solana Foundation and Google Cloud](https://x.com/SolanaFndn/status/2051698987304956281) released Pay.sh, a gateway that lets agents discover and access curated APIs through x402 or MPP, including *first-party *endpoints for Google services. A few days later, Coinbase announced that x402 discovery had been natively integrated into [Amazon Bedrock AgentCore Payments](https://x.com/coinbase/status/2052395918192722026?s=20). AWS developers now have a sanctioned path to build agents that can find services, send micropayments, transact in USDC, and operate under enterprise budgets, compliance, and audit trails.

Two weeks ago I wrote about [x402's authorization problem](https://x.com/davewardonline/status/2048049242787213330?s=20), where many live endpoints acted as unauthorized third-party wrappers in clear violation of the underlying APIs' terms of service. The risk is that the dynamic turns potential native integrators into adversaries once they see third parties collecting fees while the original providers carry the costs.

[Who Authorized This? The Gray Area of x402 on Banklessx402 needs native integrators to succeed. Unauthorized wrappers could turn potential partners into adversaries instead.![](https://static.ghost.org/v5.0.0/images/link-icon.svg)BanklessDavid Christopher![](https://storage.ghost.io/c/e4/b7/e4b77544-5a37-4f0b-8824-8440aa348476/content/images/thumbnail/who-authorized-this-the-gray-area-of-x402-1777064645.png)](https://www.bankless.com/read/who-au)Now, two weeks later, Google Cloud and AWS are directly in the agent-payment flow. I honestly did not expect that to happen this fast. There are still plenty of unauthorized endpoints circulating, but I expect their presence to accelerate agentic payments. This week may mark the next phase of x402.

But before I get too sidetracked, this [piece is about Pay.sh](http://pay.sh/): how it works, where it still needs work, and what its partner list reveals about Solana's agent ecosystem.

> Introducing [https://t.co/wP8Q8614MS](https://t.co/wP8Q8614MS), in collaboration with [@googlecloud](https://twitter.com/googlecloud?ref_src=twsrc%5Etfw)For the first time agents can discover, access, and pay-per-request for APIs from Google Cloud including Gemini, BigQuery, Vertex AI, and more using stablecoins on Solana.No accounts, no subscriptions,… [pic.twitter.com/iV6Tc1t2fc](https://t.co/iV6Tc1t2fc)— Solana Foundation (@SolanaFndn) [May 5, 2026](https://twitter.com/SolanaFndn/status/2051698987304956281?ref_src=twsrc%5Etfw)

### What Pay.sh Actually Does
Pay.sh is a discovery and access toolkit for AI agents, letting them search the catalog, find an endpoint, and pay for it.

In that broad shape, Pay.sh resembles AgentCash or Sponge, other agentic Swiss Army knives. The difference is the Google Cloud partnership: Pay.sh offers *authorized* access to Gemini, BigQuery, Vertex AI, and other Google services. [Pay.sh](http://pay.sh/) comes equipped with many endpoints beyond just Google’s. Endpoints for data, search, storage, messaging, commerce, crypto, finance, maps, media, and infrastructure. Of these, three I'm particularly excited to continue using are:

- [**Fact Check Tools**](https://pay.sh/services/solana-foundation/google/factchecktools), a free endpoint for searching Google ClaimReview fact-check data across more than 100 publishers. This lets agents check whether a claim has already been reviewed without manually searching news sites.
- [**Crush Rewards**](https://pay.sh/#catalog), for tracking retail prices across major US and Canadian stores. This lets agents compare live prices, spot deals, and monitor availability without scraping each retailer directly.
- [**BigQuery**](https://pay.sh/#catalog), a metered endpoint for running SQL over BigQuery, Google's data warehouse environment where users can run analysis on large datasets without having to build the necessary infrastructure themselves.
[![](https://storage.ghost.io/c/e4/b7/e4b77544-5a37-4f0b-8824-8440aa348476/content/images/2026/05/data-src-image-573be70c-c882-48a1-8565-28126e34bd2a.png)](https://pay.sh/)
### Where Pay.sh Still Needs Work
The first gap is pricing language.

Pay.sh is a directory of endpoint providers, and that hierarchy needs to be visible at a glance. Most providers offer a series of endpoints, some paid, some not. When a provider offers both, the catalog labels them as "free tier" but still shows a nonzero "price." A cleaner taxonomy would be three labels: free (every listed endpoint is free), metered (every listed endpoint is paid and usage-based), and mixed (the provider offers both).

[![](https://storage.ghost.io/c/e4/b7/e4b77544-5a37-4f0b-8824-8440aa348476/content/images/2026/05/data-src-image-607ceada-e615-40a0-84cf-2b78dfc4c4db.png)](https://pay.sh/#catalog)The second gap is endpoint provenance. Pay.sh has a strong native center of gravity through Google Cloud, but the broader catalog doesn't make it obvious which endpoints (beyond Google's) are first-party, which are authorized third-party integrations, and which are unauthorized. [Agentic Market](https://x.com/Nick_Prince12/status/2051727486573298072?s=20) provides a useful model for how this could look.

> we just shipped verified service filtering on agentic(.)market ☑️you can now filter to only see first-party integrations. trust at the discovery layer matters.businesses are waking up to agents being their highest upside customer segment and x402 being the rail to serve them… [pic.twitter.com/bAIhyxZYqd](https://t.co/bAIhyxZYqd)— nick.base.eth 🛡 (@Nick_Prince12) [May 5, 2026](https://twitter.com/Nick_Prince12/status/2051727486573298072?ref_src=twsrc%5Etfw)

### The Partners Around the Launch
While spearheaded by the Solana Foundation and Google Cloud, Pay.sh draws on work from a number of ecosystem teams, and that list serves as a valuable gateway into Solana's agent landscape.

[**PayAI**](https://x.com/PayAINetwork), which handles the "payment-network" layer of Pay.sh, is a Solana-first x402 facilitator. In plain terms, it shoulders the payment admin work API providers would otherwise have to build themselves to offer their services through x402: verifying an agent paid the right amount, used the right token, sent the payment to the right recipient, and confirming when the server can safely release the API response. Facilitators are optional in x402, but they make the system much easier to use. Without one, web services would have to build the blockchain infrastructure for verifying and settling payments themselves.

[**Crossmint**](https://x.com/crossmint) provides the wallet and controlled-spending layer. It builds what agents need to hold and move money safely, including virtual cards and spend controls like merchant whitelists, transaction limits, and human approvals.

[**Merit Systems**](https://x.com/merit_systems), the team behind [AgentCash](https://x.com/agentcashdev), brings the bundled-access model, the "agentic Swiss Army knife." They offer agents access to data, communication, and storage services through their own endpoints like StableCrypto, StableEmail, StablePhone, StableUpload, and StableDomains.

[**Corbits**](https://x.com/corbitsdev) sits on the provider side of Pay.sh, helping services turn APIs into agent-payable x402 endpoints. Like PayAI, it includes facilitator infrastructure for outsourced payment verification and settlement. It also provides tooling to self-host more of the x402 stack through its open-source Faremeter framework.

[**MoonPay**](https://x.com/moonpay) is the official onramp for Pay.sh, letting users show up with fiat and convert it to Solana stablecoins, like USDC or [Phantom’s CASH](https://x.com/moonpay/status/2052129029226971336?s=20).

[**Sponge**](https://x.com/paysponge)** **sits on both sides of the agent-payment flow. For agents, it provides a wallet and SDK to hold funds and pay for endpoints. For providers, Sponge Gateway helps monetize existing APIs for agents. [That makes Sponge](https://docs.paysponge.com/) part wallet, part paid-request tool, and part gateway for services selling directly to agents.

[**ATXP**](https://atxp.ai/)** **gives agents a persistent identity and payment setup they can use across services. [Agents launched through](https://docs.atxp.ai/agents) the company's tooling get an email address, a wallet, starter credits, and a connection token for SDK or CLI access. The result is a credentialed agent identity, something most other tooling stops short of constructing.

[**Tektonic**](https://x.com/TektonicCompany), the sister company of agent infrastructure provider [Clawpump](https://x.com/clawpumptech), fits in as Pay.sh’s institutional data layer. As co-founder [Bunny](https://x.com/ConejoCapital) described it to me, Tektonic focuses on institutional agents, while Clawpump handles the consumer side. Tektonic has already open-sourced its [x402 public dataset](https://tektonic.company/blog/x402-analytics-solana-base), which was built with Google Cloud’s Web3 team, including [Devan Mitchem](https://x.com/mitchem), who presented at Solana Accelerate’s demo day. A Google Cloud-native facilitator is also in the works. Together, these efforts give the ecosystem a cleaner view of x402 activity across Solana and Base, while making it easier for companies already building on Google Cloud to plug in.

Overall, the team list shows that Pay.sh is a full-stack tool for augmenting one's agents, with each company contributing a distinct layer.

### The Next Phase
Google Cloud and Amazon wouldn't be standing this close to the flow if they didn't see what we see. That alone is a phase shift from where x402 was a month ago.

What I'm still working out is the next phase. Most of the infrastructure being announced lives on the developer side. The harder problem is demonstrating agentic payments' value to the average AI user, who has no interest (yet) in SDKs or CLIs. Bridging that gap will likely come first through chat-based interfaces with endpoints built in, like AgentCash is doing with [Poncho](https://x.com/poncho_ai).

[![](https://storage.ghost.io/c/e4/b7/e4b77544-5a37-4f0b-8824-8440aa348476/content/images/2026/05/data-src-image-2ba3f0c3-5b68-464d-a958-0c8e2de73bcb.png)](https://tryponcho.com/)Hopefully Pay.sh will spin one up soon and slap a subscription model on it. Maybe reimburse you if you don't use all the credits in a month, or roll them over? That feels like a bridge in the right direction. Regardless, the increasing ease of using endpoints instead of APIs has a bright future. Make sure you're giving all the chains involved equal time of day. It's something I intend to get better at.