Developers
Your route answers with a price.
A person or an AI agent pays in USDC, then gets the response. The funds settle to the merchant receiving address.
01 · Price
GET /lookup
Host api.example.com
HTTP/1.1 402Payment Required
- Amount
- 0.02 USDC
- Pay to
- Merchant receiving address
02 · Paid response
HTTP/1.1 200OK
{
"place": "Istanbul",
"label": "Example"
}
This sample does not call a server. It shows no key.
Required, paid, and failed.
Three states of one payment. The route does not return the paid response until the payment settles.
-
Required
The price is set
HTTP 402
The route has named a price. The paid response is not sent yet.
-
Paid
The response is sent
HTTP 200
The buyer paid in USDC. The route returns the response.
-
Failed
No paid response
Payment did not settle
The route keeps the price. The buyer does not get the response.
Three paths. One checkout.
Each path uses one checkout. None of them is a new product.
-
Hosted checkout
LinkSell hosts the page. A person or an AI agent pays in USDC. The funds go to the merchant receiving address.
-
Payment link
Share one link that carries the price. The buyer pays in USDC. The funds go to the same receiving address.
-
Paid API route
Your route returns a price. After the payment, it returns the response.
Store management is separate. It does not pay a checkout.
Before you go live.
A verified receiving address, a scoped key, and a signature check.
-
Verified receiving address
Confirm the address that receives USDC before a live payment. LinkSell does not hold the funds.
-
Scoped key
Use a key that can do only the work you allow. This page shows no key value.
-
Signature check
Check the header X-X402-Signature before you trust a signed event.
Charge for your first route.
Confirm the receiving address before the first live payment.