No install. No account. No KYC. One POST from curl, a script, or an AI agent — and it settles 0.05 USDC on-chain automatically.
A "92% win rate" that nobody doubts until the money is gone. That number is usuallya future-data leak wearing a mask. leakguard finds it before you do.
$ python3 leakguard.py --demo [causality] rolling_mean: PASS [causality] rolling_corr: PASS -- suite: clean no findings -- suite: leaked-self [LEAK] perfect_separation: AUC=1.000 RESULT: PASS
Every detector is validated against a freshly injected bug, never a historicalcasualty. And the rolling aggregates carry a perturb-future assertion: perturb the tail,recompute, and the earlier output must be bit-identical. Non-causality fails loudlyinstead of producing a wrong number quietly.
It caught three real defects in its own code the first time it ran.
Single file, stdlib only. Runs anywhere Python 3.9+ does.
The service is live right now. Send it any series and see what it says:
curl -s https://www.web3id.xyz/x402/audit \
-H 'content-type: application/json' \
-d '{"y":[0.1,0.2,-0.1,0.3,-0.2,0.4],"fwd_view":[0.1,0.2,-0.1,0.3,-0.2,0.4]}'
Unpaid, it returns 402 with the exact payment challenge — that is the
point: it answers nobody until it is paid. Pay the challenge and the same request
returns the full audit. Verification of the client itself needs no wallet:
python3 buyer.py --self-test runs 14 checks against live mainnet.
Pay to the address below, then email your tx signature or contact with it. Filedelivered immediately, no account, no KYC, no platform in between.
Solana · verify before paying ·mainnet address, SPL-compatible for USDC
The buyer client is self-tested against mainnet: it builds and simulates a real SPL TransferChecked, and the transfer leg returns err=null against a funded account. Nothing here is aspirational.
curl -sO https://www.web3id.xyz/store/buyer.py python3 buyer.py --self-test # 14/14 PASS, no wallet required python3 buyer.py --url https://www.web3id.xyz/x402/audit --series "1.0,2.0,3.0,4.0,5.0"
One file. It reads the 402 challenge, serializes the payment by hand (no SDK, no dependencies beyond the stdlib), signs with your key, submits it, waits for confirmation, then replays your request with the settlement and prints the audit. One file, all yours, fully auditable — read it before you trust it with a key. Point --keyfile at your Solana keypair.
Alternatively, pay the address above with any wallet that supports SPL tokens and send the tx signature — the audit is delivered either way.
No account, no KYC, no platform in between. The payer creates the associated token account and pays rent (so it works even at 0 SOL).