Skip to content

Examples ​

Thirty runnable recipes, grouped in three pages. Every command is verified against the implementation; where a recipe needs credentials or infrastructure this is stated up front, and no output is shown that we have not either captured or pinned in tests. Recipes involving real funds carry a risk block — read it before running anything that signs.

#RecipePageNeeds credentials?
1First-time install (npm)SetupNo
2Windows PowerShell installSetupNo
3macOS / Linux quick installSetupNo
4CLI authentication (device + headless OTP)SetupHosted account
5Wallet connection (extension / SEP-7)SetupNo
6Hardware wallet (Ledger) setupSetupLedger device
7Import an encrypted wallet (stdin only)SetupYour key
8Create an agent wallet + spending policySetupNo
9Read-only MCP configurationSetupNo
10Execution-enabled MCP configurationSetupAgent policy
11Two-phase transaction confirmationTrading & dataAgent policy
12x402 payment challenge (labeled simulated)Trading & dataNo
13Stellar SDEX trading (labeled simulation)Trading & dataNo
14Hyperliquid market dataTrading & dataNo
15Hyperliquid signed perp orderTrading & dataSigner — real funds
16Hyperliquid shortingTrading & dataSigner — real funds
17HLP vault informationTrading & dataNo
18HLP deposit / withdrawTrading & dataSigner — real funds
19Binance testnet configurationOps & analysisBinance testnet keys
20Binance spot orders (gated)Ops & analysisBinance keys
21Escrow lifecycle (local ledger)Ops & analysisNo
22Transaction verification (honest semantics)Ops & analysisNo
23Solana read-only queriesOps & analysisNo
24Oracle price queries + disagreement gateOps & analysisNo
25Quantitative market analysis (offline)Ops & analysisSupplied data files
26Fork replay-risk inspectionOps & analysisNo
27Configuration validationOps & analysisNo
28Automated diagnostics (doctor)Ops & analysisNo
29Self-update and rollbackOps & analysisnpm install
30UninstallationOps & analysisNo

Conventions used everywhere:

  • Placeholders (<G...>, 0x…, <uuid>) must be replaced with your values. No real keys, seed phrases, or production credentials appear in these pages — ever.
  • Status labels (LIVE / SIMULATED / LOCAL / BLOCKED) follow the Honesty Matrix and are printed by the CLI itself alongside results.
  • Nothing here weakens a gate: recipes that move value say so, and the gates (risk engine, mandate policy, live master gate) are shown as they behave, not bypassed.

FurlPay CLI is non-custodial software. Every execution surface is labeled live or simulated at runtime.