The future, let the AI Agent pay for us now!

Have you ever wondered? We know a lot of different response codes from the back of the house, like 4xx would have 400 401 403 404, what is 402? So where did it go? Let's learn.

With "pay.sh: Enabled AI Agents with x402 Micropayments - Learn how to make your AI Agents transaction with a new standard on Solana" at "Solana x AI Builders: The Road to Mainnet # 2 (Bangkok)" by Mr. Golf from ByteCat last Sunday. Confused. (Do not slow down. Huh?)

.

📜 The 30-year story of HTTP 402.

Of course, we Dev's probably already know the response code. There will be 200 OK, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, which 402 Payment Required. It came with friends. In 1997, the new Internet Explorer arrived.

By the 402 Payment Required, it is thought that if one day the Internet is used until it is very mass, someone will pay through http, so declare 402 to use a particular payment, which is placed as a pay-per-content purchase, such as buying a movie, buying a song, how to pay? And what is the protocol?

And the 402 is not in widespread use because

1. The spec does not tell you the details inside, but how to do it. There are no standards to use.

2. But the various payments can be made by subscription instead. It is good for business to be able to estimate revenue and the user decides to subscript 1 month because

3. Humans have decision fatigue, make decisions often, use a lot of energy, it is tired, so they can not pay.

And each response code 402 is not implemented as originally designed.

- Shopify: Store frozen (unpaid bill) Store not paid

- Stripe: Failed card charge. Can't cut money.

- Google API: Quota exceeded using quota.

And flow payments are designed for humans. And what if not humans?

Of course, no one has never heard of an AI Agent. It is the job of being a personal secretary to do this, such as helping research, summarizing, analyzing things. Of course, it works unscrupulously, working without thinking, just following the rules and without decision fatigue.

When we order AI to work, when paying, there is a problem: he cannot use our credit card if we call API once 0.001 $, but the credit card fee is 0.30 $, which is 300 times higher than the fee, so it is not worth having our AI Agent use our credit card, and KYC, chargebacks, account setup, and so on.

.

🪙🤖 Why crypto + Al woke it up

What if you pay with a script instead?

Of course, we can create a wallet. No need to go to KYC, top up the AI to make him decide and pay. Also, the fee is very cheap. If paid with USDC on Solana, the fee is only $0.00025, which is less than a cent of Thai money. No account required. The transaction takes less than 1 second.

We can set a time and give us an agent sign signature and execute immediately.

⌛ Timeline: Because humans have trouble making decisions, but AI doesn't think about them.

- Coinbase x402 (OCT 2025): Announced at the end of last year. It is Native USDC first.

- Coinbase x402 V2 (OCT 2025): Supports all ERC-20, SPL, Token2022 and a variety of chains, including Base, Solana, Etheruem, Polygon, Arbiturm, Wrold, AI Agent payment without human involvement (payment layer AI Agent)

- Stripe + Tempo (MAR 2026): Machine Payments Protocol (MPP), in addition to supporting stable coin, also supports fiat, Bitcoin Lightning (or Bitcoiner, they like zap, this one) on Tempo, Base, Solana.

- Pay.sh (MAY 2027): This one of Team Solana.

.

👖 How pay.sh fits in

Originally, the AI Agent knew everything before paying, so Solana placed himself as a payment layer that didn't have to know how each line worked. It would manage to get the AI Agent to run through this one. No need to learn a new pay line, it would manage.

Components of Pay.sh

1. Pay CLI: local tool

2.Catalog: There are 72 services for the AI Agent to do some work, such as fetch the price of the scripto. There is a cost to fetch. See if we will pay, and we can create these tools as well.

3.Protocol layer: detect what the payable layer is, such as x402 to MPP, as well as new standards that will emerge in the future.

402 Lifecycle: The client here is an agent, runs the API and gets the 402 and challenge back, then asks for approval to pay, then signs to confirm the transaction, and finally gets the 200 back with the content we bought back.

The signing signature of the transaction uses a private key that the pay.sh does not hold for us, and if pay.sh hit anything, our money is still in the wallet.

So what services are there in catalog? Let NotebookLM help to summarize it.

- AI / ML 33 services

- Data & Search 15 services

- Messaging 9 services

- Crypto & Compute 7services

Why is that interesting?

- No people involved (or no human-in-the-loop) except for the sign, which we can make as a programmatic, can put the private key in the secret manager and all this.

- If there's a protocol, don't learn again. It adds knowledge.

- There's a catalog.

- Designed as an AI Agent in use only.

- There's a sandbox to try before you use it.

It connects the AI Agent to the payment layer.

.

🏗️ Build your own paid API.

For example, analyze the market (at first glance, the price of Krypto, no?), go to see the place, view the review, see the neighbors, take to make a picture and send it to the email, all happened on the pay protocol, no one was involved.

We can create an AI Agent, open an API, take up a catalog, and then the user can access our API through paying as a P2P agent economy.

There's a built-in MCP. There's a config for us to add ourselves to 'mcp.json'.

Or create a pay-as-you-go API, retrieve the price, return the price, and have a pay gateway to write the file 'Provide.yml' indicating how many baht each endpoint collects per request.

- So where is the real API? It's at 'routine.url'. What line does each endpoint have? How much does it cost?

- People access through the gateway and then enter the proxy to enter the API again.

- This gateway covers the original API to give the AI Agent access.

Capped ideas

- Real-time DEX aggregator

- On-chain analytics wallet behavior

- Al trading signals

- NFT metadata service

- Cross-chain bridge quotes

- DeFi risk scoring.

- P2P Agent Economy.

Big companies provide. If little people do and collect money, they can do it.

.

💬 Recap.

- HTTP 402 since 1997 but not widely used.

- AI Agent + crypto solves the problem.

- pay.sh a new payment layer in the agent era.

- There are 72 services available and available for MCP.

- Our API can be used as a money storage API. It can be called monetized by our existing API. Hahahahaha

.

💬 Q & A

- Can I use it to make purchases like buying macbooks or shopping online on leading platforms? AI Agents can't access our accounts, including our money. This is a flow designed for people to use, not AI Agents right now. But if we can do this system, we can fight big platforms.

- When you top up your wallet, you have to have that currency before you challenge it, but you can support many currencies. In the future, someone can make an auto conversion.

- pay.sh don't hold the private key, and the private key is still with us.

.

# lemon 8 club # Club, games and tech # Includes IT matters # Lemon 8 Howtoo # Share IT Trick