Paste your API URL, set a price per request, and launch. We handle payments and settlement.
Launch your APIPOST /x402/weather-ai content-type: application/json { "city": "Bengaluru" }
We built infrastructure for direct, onchain digital-content payments. A creator sets the content and the price, a buyer pays from their own wallet, the money goes straight to the creator, and the application only releases the content once it has verified the transfer on chain.
Bring the API you already run. Everything between the request and the payout is handled for you.
We publish a protected gateway in its place. Buyers and agents call the gateway; only a verified payment reaches your real API.
The server re-reads the transaction receipt and matches the chain, recipient, token and exact amount before anything is delivered.
The receipt is written before your content is served, so the same proof recovers the same purchase — and can never buy a different one.
Meter an API, lock a file, or let an autonomous agent pay its own way.
Set a price as small as a fraction of a cent. Callers pay for exactly what they use, with no subscription and no API-key checkout.
Upload a report, a dataset, code, or private notes. The file is encrypted at rest and released only after the payment clears.
1GET /api/paywalls/:id/download 2402 Payment Required 3GET … PAYMENT-SIGNATURE: <proof> 4200 OK — file decryptedContent is never stored in the clear.
An autonomous agent reads the 402 challenge, sends the transfer, and retries with the proof. No account, no key, no human in the loop.
Paid requests, revenue and status for every listing. Pause, resume, reprice or delete — each action signed by your wallet.
No custody, no payout schedule, no platform cut between you and the buyer.
Buyers transfer straight to the address you configured. We never hold your funds.
The facilitator fee is 0%. You pay network gas, and nothing to us.
Paid requests, revenue and status are tracked per listing and shown publicly.
Signed listings, encrypted storage, exact-amount checks and replay control.
From an endpoint you already run to a paid product, in a few minutes.
Give us the URL you already serve. We keep it private and publish a protected gateway in front of it.
Choose the methods and the amount, then sign with your wallet. Signing proves ownership; it does not move funds.
Your API appears in the marketplace and the discovery feed. Every verified payment settles directly to you.
A payment proof is a transaction hash. Anyone can check it on the public explorer.
The client calls the resource with no proof and receives HTTP 402 carrying the exact network, token, amount and recipient.
The buyer's wallet sends that exact transfer on chain. Nothing is escrowed — the funds go straight to the creator's address.
The proof — scheme, transaction hash and payer — is base64-encoded into the PAYMENT-SIGNATURE header and the call is retried.
The server re-reads the receipt on chain, checks every field of the requirement, stores a durable receipt and only then delivers.
We do not take a cut and we never hold your money. You pay network gas, like any on-chain transfer.
Meter an endpoint you already run and get paid per request.
Launch your API IncludedPut a paywall on a document, a dataset or private text.
Create a paywall IncludedConsume paid resources programmatically, with no account to create.
Read the docs IncludedIt is configured for Robinhood Chain (chain ID 4663) and Robinhood Chain Testnet (46630). A deployment serves one network at a time, and testnet records are kept in a separate store.
Native ETH is supported by default. ERC-20 currencies — Global Dollar (USDG) on mainnet — are available only when the operator has configured a verified contract address for that exact network.
No. The buyer transfers directly to the creator address named in the payment requirement. The application verifies the transaction and reports a facilitator fee of zero.
Usually not. Check every wallet confirmation carefully — network, recipient, token and amount — and contact the creator directly about any refund request.
No certification or drop-in compatibility is claimed. The application uses a custom HTTP 402 challenge and payment-proof format inspired by x402, and the docs say so explicitly.
The settlement receipt is stored before the content is served. Reopening the link and presenting the same proof recovers the same purchase — and that proof can never unlock a different resource.
No independent audit has been published. The safeguards in place are listed in the security section of the docs, along with the known operational limits. Do not assume an independent review has taken place.
Bring an endpoint, a dataset or a document. Put a price on it and let the payment rail do the rest.
