You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optional, low-key qscli subcommand to fund a key over x402 (USDC on Base) —
so an autonomous/headless agent can self-provision inference credit without a
human opening a card. Mirrors the website's low-key treatment (see the x402 docs
page and backend #257): available to the agent/headless crowd, invisible to the
mainstream CLI user.
This is a fast-follow, not MVP. Anyone can already script the top-up today
with the standalone reference client (x402/deploy/pay.py pattern) against POST https://pay.quicksilverpro.io/x402/topup/{1,5,10}. A CLI subcommand is a
convenience, not a gap.
Scope
qscli topup --x402 [--amount 1|5|10] (or qscli x402 buy <amount>): runs
the 402 → sign → retry handshake and prints/stores the minted key.
Lazy dependency: put x402 + eth_account behind an extra — pip install quicksilverpro[x402] — and import them inside the
subcommand only. The default install must not pull crypto deps or grow.
Key handling (security-critical): read the payer wallet key from an env
var only (e.g. QSP_X402_WALLET_KEY). Never persist it, never write it
to config, never log it. This is the biggest risk surface — design first.
Low-key surface: keep it out of the top-level --help for mainstream
users (or gate visibility); no USDC/crypto wording in the default UX. Same
anti-scam framing the website uses.
On success, offer to write the returned sk-... into the usual CLI key
config (the standard flow), so subsequent calls "just work".
Goal
Optional, low-key
qsclisubcommand to fund a key over x402 (USDC on Base) —so an autonomous/headless agent can self-provision inference credit without a
human opening a card. Mirrors the website's low-key treatment (see the x402 docs
page and backend #257): available to the agent/headless crowd, invisible to the
mainstream CLI user.
This is a fast-follow, not MVP. Anyone can already script the top-up today
with the standalone reference client (
x402/deploy/pay.pypattern) againstPOST https://pay.quicksilverpro.io/x402/topup/{1,5,10}. A CLI subcommand is aconvenience, not a gap.
Scope
qscli topup --x402 [--amount 1|5|10](orqscli x402 buy <amount>): runsthe 402 → sign → retry handshake and prints/stores the minted key.
x402+eth_accountbehind an extra —pip install quicksilverpro[x402]— and import them inside thesubcommand only. The default install must not pull crypto deps or grow.
var only (e.g.
QSP_X402_WALLET_KEY). Never persist it, never write itto config, never log it. This is the biggest risk surface — design first.
--helpfor mainstreamusers (or gate visibility); no USDC/crypto wording in the default UX. Same
anti-scam framing the website uses.
sk-...into the usual CLI keyconfig (the standard flow), so subsequent calls "just work".
Why gated / not now
"looks scammy" perception we deliberately avoid on the site.
and we see real agent traffic on the x402 endpoint.
Related
(discoverability), ecosystem: add QuickSilver Pro (Services/Endpoints) coinbase/x402#281 (ecosystem listing).