Docs
How the 402 handshake works
kite402 wraps any URL you own behind the x402 payment protocol. This page walks through the request lifecycle end to end.
1. Register an endpoint
From the dashboard, paste the URL you want to protect and set a price in HBAR and/or USDC. You get back an agent URL and a human paywall URL.
2. Unpaid requests get a 402
GET the agent URL without payment and the gateway responds 402 Payment Required, with the accepted assets and destination account in the body.
3. Pay over x402, retry
Construct a payment payload with the x402 client SDK, sign it, and attach it as a PAYMENT-SIGNATURE header. Retry the request — the gateway verifies, settles on Hedera, and proxies your response.
4. Verify the receipt
Every paid response includes an X-HCS-Sequence header. Look it up on the public HCS topic (linked in the footer) on HashScan to confirm the settlement independently.
GET /p/wx7Kd91k2A
402 Payment Required
accepts: 0.1 HBAR · 0.001 USDC → 0.0.9693516
PAYMENT-SIGNATURE: eyJ4NDAyVmVyc2lvbiI6Mi4uLg
payer signs · facilitator settles on-chain
GET /p/wx7Kd91k2A (retry)
200 OK
X-HCS-Sequence: 4 · X-X402-Receipt: eyJhbGciOi…