One payment link. People can pay it, and AI agents can pay it.
AI agents already call your API. They can't sign up or hold a card, so today they drain your free tier or leave. checkout402 gives you one link an agent can pay on its own. The agent gets the goods, you get the money, and it all happens in one round trip. No account on their side, ever.
An agent finds your checkout and pays it on the spot. No account, no card, no key from you. The price arrives as an HTTP 402, the web's built-in "payment required" answer.
One question decides it: where does the thing you sell live? Price, payout and receipts are the same in all four.
Also you rarely name the type: a payload means inline, a URL means relay, a URL and a tool name means mcp. Only webhook is said out loud.
Fulfilment modes, in full→Settling a payment on-chain (on the public payment network) costs about a cent, whatever the amount. A one-cent sale only works when one settlement covers many calls.
A package is paid for once and spends down a counter. The buyer gets a pk_… key and calls until it runs out. No signature, no wait after the first. That is what makes $0.001 a call possible, and it is why the minimum on a package is $1.00 while a single call has no minimum at all: a cheap one-off is how a buyer tries you before committing.
You keep your Stripe billing, your keys and your contracts. This is a surface for the demand you currently turn away, not a migration.
You can see them in the logs and you cannot bill them, because they can't hold an account. A 402 turns that traffic into revenue instead of cost.
Wrap it behind relay fulfillment. Unpaying agents get a 402; paying ones get the response. Nothing about your server changes.
Card networks can't price a $0.002 lookup. The fee is bigger than the sale. Sell 1,000 calls as one package: one settlement, one fee, fractions of a cent each.
License keys, datasets, downloads. Stored inline, released only after the money lands.
Also works agent → agent, with no browser on either side · humans on the same URL, signing the same payment · checkout.paid webhooks, fired after settlement
The selling guide→Payout goes to your wallet: hardware, Safe, whatever you trust. checkout402 holds no buyer or seller keys. The only key we hold pays the network's transaction fees.
Goods go out only after the money has landed. The wrong order is not a bug we could ship; the system cannot represent it.
One rate, added on top of your price. The fee is a line on the buyer's bill, not a deduction from yours.
# 1. create a checkout. your wallet address is the only setup curl -X POST https://api.checkout402.com/v1/checkouts \ -H 'Authorization: Bearer c402_live_…' -H 'Content-Type: application/json' \ -d '{"title":"Pro license","price_usd":"49.00", "pay_to":"0xYourWallet","payload":{"license_key":"…"}}' # 2. share the URL. humans open it, agents get a 402 and pay
Sellers: point an MCP host at https://api.checkout402.com/mcp. Buyers: pay402 turns any checkout URL into one call.
Connect it to Claude Code, or to regular Claude as a custom connector, and create and manage checkouts by asking. Any MCP-speaking agent can buy from one without a connector at all.
Connect Claude→