Wicket
Launch app
Early access

Wrap any URL or API in a pay-per-request x402 gate in five minutes, with a public counter of verified paid requests.

Usage numbers come from onchain settlements and can be checked by anyone, not from a self-reported dashboard. Setup takes minutes and needs no code changes on the origin API.

Launch app Read the docs
Paste an origin URL, set a price per request in USDC, and get a gated proxy URL that returns 402 until paidPayout straight to the owner's own wallet, so Wicket never holds fundsPublic page per gate with verified paid request count, unique payers and settlement linksTest mode with a sample agent client so owners can confirm the flow before going liveEmbeddable badge that reads the live counter from onchain records

What you get with Wicket.

Built for aPI owners, indie developers selling data or tools to agents, and projects that want to show real paid usage.

  • Paste an origin URL, set a price per request in USDC, and get a gated proxy URL that returns 402 until paid

    Planned

  • Payout straight to the owner's own wallet, so Wicket never holds funds

    Planned

  • Public page per gate with verified paid request count, unique payers and settlement links

    Planned

  • Test mode with a sample agent client so owners can confirm the flow before going live

    Planned

  • Embeddable badge that reads the live counter from onchain records

    Planned
01

Payout straight to the owner's own wallet, so Wicket never holds funds.

Each payment settles in USDC straight to the address you set. Wicket only reads the settlement to verify and count it, so there is no balance to withdraw and nothing to trust us with.

Planned

Payout routing for forecast-tiles

9vQe...Bq2MPayout wallet
0.26 USDCSettled to wallet
0 USDCHeld by Wicket
~1 slotSettlement time
02

Paste an origin URL, set a price per request in USDC, and get a gated proxy URL that returns 402 until paid.

Wicket gives you a proxy URL in front of your origin. Any request without a valid USDC payment gets an x402 response describing the price and where to pay. Paid requests are forwarded untouched, so your API needs no code changes.

Planned

Create a gate

Results appear here.
03

Public page per gate with verified paid request count, unique payers and settlement links.

Every gate gets a public page with the verified paid request count, unique payers and a Solscan link for each settlement. Visitors do not have to take your word for the numbers.

Planned

wicket.gate/lexicon-lookup (public)

MetricValueSource
Verified paid requests61Solana settlements
Unique payers3Distinct wallets
First paid request8 days agoSolscan
Latest settlementToday 14:19Solscan
04

Test mode with a sample agent client so owners can confirm the flow before going live.

Run the built-in test agent against your gate. It receives the 402, pays a small test amount, retries and shows you the origin response. Test payments are kept out of the public counter.

Planned

Test agent run on geo-batch

GET /batch returned 402. Price: 0.005 USDC to 9vQe...Bq2M.
Test agent paid and retried. Origin responded 200 with 412 bytes.
Is that counted publicly?
No. Test runs stay private until you switch the gate to Live.
05

Embeddable badge that reads the live counter from onchain records.

Drop one snippet on your site or README. The badge fetches the current verified count from onchain records each time it loads, so it cannot drift from what actually settled.

Planned

Badge snippet

html
<a href="https://wicket.gate/forecast-tiles">
  <img src="https://wicket.gate/badge/forecast-tiles.svg"
       alt="128 verified paid requests" />
</a>

Usage numbers come from onchain settlements and can be checked by anyone, not from a self-reported dashboard. Setup takes minutes and needs no code changes on the origin API.

3 steps from start to first result.

Wrap your originPaste the URL of your API, choose a USDC price per request and connect Phantom,
Test, then go liveRun the test agent to see the 402, the payment and the origin response. When it
Show verified usagePublish the gate page or embed the badge. The counts come from Solana settlement

Open by default.

Every screen reads from the same model. Live parts read public onchain data; nothing ever asks your wallet to sign.

Read the docs
wicket.json
{
  "product": "Wicket",
  "network": "solana",
  "features": [
    {
      "name": "Paste an origin URL, set a price per request in ",
      "status": "planned"
    },
    {
      "name": "Payout straight to the owner's own wallet, so Wi",
      "status": "planned"
    },
    {
      "name": "Public page per gate with verified paid request ",
      "status": "planned"
    },
    {
      "name": "Test mode with a sample agent client so owners c",
      "status": "planned"
    }
  ]
}

What works today.

Live features work today. Planned ones are next on the roadmap, in this order.

Paste an origin URL, set a price per request in USDC, and get a gated proxy URL that returns 402 until paidPlanned
Payout straight to the owner's own wallet, so Wicket never holds fundsPlanned
Public page per gate with verified paid request count, unique payers and settlement linksPlanned
Test mode with a sample agent client so owners can confirm the flow before going livePlanned
Embeddable badge that reads the live counter from onchain recordsPlanned

Questions.

Short answers. The docs have the rest.

What is Wicket?

Wrap any URL or API in a pay-per-request x402 gate in five minutes, with a public counter of verified paid requests. Usage numbers come from onchain settlements and can be checked by anyone, not from a self-reported dashboard. Setup takes minutes and needs no code changes on the origin API.

What works today?

Wicket is in development. Every feature is on the status list with what ships next, and the app opens in a sample workspace so you can see how it will work.

Do I need a wallet?

No. You can explore without one. Connecting a Solana wallet only shares your public address so Wicket can read your balances; it never asks you to sign a transaction.

Who is it for?

API owners, indie developers selling data or tools to agents, and projects that want to show real paid usage.

Paste an origin URL, set a price per request in USDC, and get a gated proxy URL that returns 402 until paid.

Wrap any URL or API in a pay-per-request x402 gate in five minutes, with a public counter of verified paid requests.

Launch appRead the docs