Quorlet
Official CA
HTTP 402 · SOL & USDC

Put an x402 paywall on anything. Get paid on Solana.

Gate a secret, a link or a file behind a real HTTP 402 response. Buyers pay straight to your wallet and every payment is verified on-chain before anything is unlocked.

Create a paywallInspect an endpoint
Official CA6Z6fbWvBdhfedN4kpVxUwzy4rkUWM9Db5mAQZ1o8pumpSolscanDexScreener

Try it live

Hit a real HTTP 402 yourself.

Every Quorlet paywall exposes an endpoint that answers with a standard 402 Payment Required and machine-readable payment terms. Paste any paywall or x402 URL, or create your own.

Connect your wallet to use your latest paywall, or paste a URL.

curl -i <paywall url>

Press the button to send a request.

Use cases

Anything worth paying for can sit behind a 402.

  • Paid APIs for AI agents

    Let agents pay per request with no accounts, API keys or invoices. The 402 response tells them exactly what to pay.

  • Digital downloads

    Sell a PDF, dataset, template or course file. The download link is released only after the payment is confirmed on-chain.

  • Secrets and license keys

    Hand out a key, invite code or credential to whoever pays. Nothing is revealed to the browser before verification.

  • Gated links and invites

    Protect a private Discord, Telegram or Notion URL. Buyers pay once and get redirected straight in.

  • Premium content

    Charge for a single article, report or alpha post without building subscriptions or a checkout.

  • Micropayments

    Solana fees are a fraction of a cent, so charging a few cents per unlock actually makes sense.

How it works

Three steps from idea to income.

  1. 01

    Create

    Set a title, the content to protect, a price in SOL or USDC and your recipient wallet.

  2. 02

    Share link

    Get a /p/ page for humans and an /api/x402/ endpoint for agents and scripts.

  3. 03

    Buyer pays & unlocks

    The buyer signs one transaction. We verify it on-chain, then release the content.

The 402 flow

Without proof of payment, the endpoint answers 402 with machine-readable requirements, including a one-time reference key. The buyer sends a transfer that includes that key, then repeats the request with the transaction signature. We fetch the transaction from Solana RPC and check that it succeeded, contains the reference, paid the recipient at least the price, and has not been used before.

GET /api/x402/<paywall-id>
-> 402 Payment Required
   PAYMENT-REQUIRED: <base64 of the JSON body>
GET /api/x402/<paywall-id>
X-PAYMENT-SIGNATURE: <transaction signature>
-> 200 OK
   PAYMENT-RESPONSE: <base64 {success, signature, network, payer}>

402 response body (shape; values in angle brackets are filled per paywall)

{
  "x402Version": 2,
  "error": "Payment required",
  "accepts": [
    {
      "scheme": "exact",
      "network": "solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1",
      "asset": "SOL",
      "amount": "10000000",
      "payTo": "<recipient wallet>",
      "resource": "https://<host>/api/x402/<paywall-id>",
      "description": "<paywall title>",
      "maxTimeoutSeconds": 600,
      "extra": {
        "reference": "<fresh public key per request>",
        "decimals": 9,
        "symbol": "SOL",
        "memo": "quorlet:<paywall-id>"
      }
    }
  ]
}
Platform fee
0%

Platform fee

Solana finality feel
< 1s

Solana finality feel

Currencies: SOL and USDC
2

Currencies: SOL and USDC

Verified on-chain
100%

Verified on-chain

Built for trust

Secure by default, simple to run.

  • Non-custodial

    Funds go straight from the buyer to your wallet. Quorlet never holds your money.

  • Server-side verification

    Amount, recipient, currency and a unique reference are all checked on-chain before anything unlocks.

  • Replay protection

    Each transaction signature unlocks one paywall. Reusing a payment elsewhere is rejected.

  • Verifiable receipts

    Paste any signature into the receipt checker to confirm who paid whom and how much.

  • Endpoint inspector

    Point the inspector at any x402 URL to decode its payment terms and check it is well formed.

  • Devnet and mainnet

    Test the whole flow with free devnet SOL, then switch the paywall to mainnet when you are ready.

Questions, answered

What is x402?

x402 uses the long-reserved HTTP 402 Payment Required status. A server answers with the price and where to pay; the client pays and retries, and the server unlocks the resource.

Who holds the money?

You do. Buyers pay directly to the wallet address you set. Quorlet only verifies the transaction and never has custody.

Do buyers need an account?

No. A Solana wallet is enough. For agents and scripts, the API endpoint works without any sign-up.

Do I need an account to create a paywall?

Connect a wallet to create and manage paywalls. You can optionally sign up with email to keep them tied to your profile.

Can I test without real money?

Yes. Create the paywall on devnet and pay with free test SOL, then recreate it on mainnet when you are ready.

Is the secret safe before payment?

The protected content is stored server-side and only returned by the endpoint after the payment has been verified on-chain.

Ready to get paid for what you make?

Create your first paywall in under a minute. No platform fee, no custody.

Create a paywallRead the docs