FurlPay Docs
Open App
  • Services & Availability
  • Quickstart
  • For AI Agents
  • FurlPay CLInew
  • Installationnew
  • CLI Quickstartnew
  • MCP Server & Agent Securitynew
  • Tradingnew
  • Escrow & Verificationnew
  • Monorepo
  • API Routes
  • Authenticationupdated
  • Webhook Eventsupdated
  • Error Codesupdated
  • Rate Limitsnew
  • Configuration & Setupnew
  • Merchant Paymentsnew
  • Payroll & Payoutsnew
  • Agentic Payments (x402)updated
  • Agent Trust & Mandates (TAP)updated
  • CCTP Cross-Chainupdated
  • LI.FI Swapsupdated
  • FurlPay Travels (Travel MCP)updated
  • Solana Actions & Blinks
  • Settlement Workspacenew
  • FURL Tokennew
  • Claude Connectorupdated
  • AI Assistants
  • Circlenew
  • Ramp Providersnew
  • Telegram Mini Appnew
  • Stripe Crypto
  • Persona KYC
  • Regulatory status
  • Screening & Casesnew
  • Security Postureupdated
  • Signing & WebAuthnupdated
  • Help Center
  • Getting Started
  • KYC Verification
  • Passkeys & Biometrics
  • Privacy & Data Protection
  • Transaction Statuses
  • Gasless Transfers
  • Deposits & Withdrawals
  • Managing Virtual Cards
  • Freezing & Unfreezing Cards
  • Declined Transactions
  • SDK & API Support
  • x402 Monetization Basics
  • Booking Travel
  • Travel Refunds & Cancellations

Resources

  • Changelog
  • System Status
  • OpenAPI Spec
  • Community
  • GitHub
Docs/CLI/Trading

CLI

Trading with the CLI

One CLI, two very different execution realities: Hyperliquid perpetuals are live and signed — real orders that require a signer — while Stellar SDEX and Soroban order flow is a deterministic local simulation in this build. Every command below carries its status at runtime.

The one-sentence summary

furlpay hyperliquid trade places real orders and moves real money. furlpay trade limit (Stellar) does not place an order anywhere — it runs a labeled local simulation and broadcasts nothing. Do not treat the second as a rehearsal for the first.

Hyperliquid L1 — live execution

LIVEmarket dataLIVE (SIGNED)execution & vault transfers

Connectivity and market data

bash
furlpay hyperliquid status      # validator connectivity, active universe, HLP vault
furlpay hyperliquid markets     # tradeable perps: mark price, funding, open interest
furlpay market BTC              # realtime L2 book, depth bands (10/25/50 bps), OFI, micro-price
furlpay market BTC --slippage 0.5 --side buy

Read-only market data needs no credentials. The microstructure metrics (order-flow imbalance, volume-weighted spread, depth-weighted micro-price) are computed from live /info responses.

Perpetual execution

bash
furlpay hyperliquid trade --symbol BTC --side buy --size 0.05 --leverage 5 --limit 75000
furlpay account balance
furlpay account positions
  • Orders are real EIP-712 Phantom-Agent L1 submissions signed locally.
  • The signer comes from the environment: HYPERLIQUID_PRIVATE_KEY or ETH_PRIVATE_KEY — never a command-line argument, never a file the docs example writes.
  • Fail closed: without a configured signer, execution commands refuse to run rather than degrade into a simulation.
  • The pre-trade risk engine enforces your configured limits before an order is built.

Pre-trade risk controls and the kill switch

bash
furlpay trading limits --max-single-order 50000 --max-leverage 20
furlpay trading kill-switch --symbol BTC

The kill switch blocks new trades and cancels active orders for the symbol (all markets if omitted). The same control is exposed to agents as furlpay_emergency_stop — a human-approval-gated MCP tool.

HLP clearinghouse vault

bash
furlpay earn hlp stats
furlpay earn hlp deposit 1000
furlpay earn hlp withdraw 100
  • Stats derive equity, APY and all-time PnL from the live /info vault response. Fields the public API does not report (share price, open position count) are shown as unavailable — never fabricated benchmarks.
  • Deposits and withdrawals are real signed vaultTransfer actions, strictly require the configured signer, and carry a 4-day lockup.

Stellar — labeled local simulation

SIMULATEDSDEX order flow · Soroban swapsNOT IMPLEMENTEDSEP-8 issuer authorization
bash
# SDEX limit order — LOCAL SIMULATION: nothing is broadcast
furlpay trade limit \
  --side buy \
  --asset JQQQ:GDXFE4P76X667RKYHVMZ4H5XQWPLK3X72Z7YXZGHK8R5M7OQ3V7QJQQQ \
  --against USDC:GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN \
  --amount 25 \
  --price 104.20 \
  --sponsor

# Path payment strict send with dest_min slippage protection — simulated
furlpay trade market-buy --asset JQQQ:GDXFE4P76X667RKYHVMZ4H5XQWPLK3X72Z7YXZGHK8R5M7OQ3V7QJQQQ \
  --with USDC --spend 1000.00 --slippage 0.5 --sponsor

# Soroban AMM swap with pre-flight gas simulation — simulated
furlpay trade swap --pool-id <pool> --sell-asset USDC --sell-amount 500 --min-receive 4.88 --asset FOBXX

# Order management — simulated
furlpay order list --pair JQQQ/USDC
furlpay order inspect --offer-id 8829104
furlpay order cancel --offer-id 8829104 --sponsor
furlpay order cancel-all --pair NVDA/USDC

Results are deterministic local simulations of Horizon/Soroban submission. Regulated-asset trade results carry sep8Status: "not_performed" — compliance is never claimed. The registry behind furlpay rwa list carries no hardcoded APY and no invented approval-server URLs.

Tokenized equities & RWAs

bash
furlpay rwa list --category equities,treasuries
furlpay rwa inspect --asset JQQQ
furlpay rwa inspect --asset FOBXX

Inspect surfaces SEP-8 issuer-authorization requirements for regulated tokenized equities (JQQQ, Securitize NVDA) and money market funds (FOBXX, USTBL) — what the issuer requires, not an approval. The KYC command is not implemented in this build: it prints what must be verified with the issuer and exits non-zero. It never reports an approval.

bash
furlpay rwa kyc --asset FOBXX --interactive   # exits 1 — NOT_IMPLEMENTED

Market data and simulations are not trade confirmations

A quote, a preview or a simulated fill is not evidence that anything traded. Only a verification against the executing network proves an order: furlpay tx verify for Stellar history, furlpay account orders and furlpay account positions for live Hyperliquid state.
Did this page help?
Edit this page on GitHub

← Previous

MCP Server & Agent Security

Next →

Escrow & Verification