Stock tickers in crypto context: AAPL, TSLA, NVDAx, trending stocks
Requires logged-in CLI: check ~/.minara/credentials.json; if missing → minara login (prefer device code). If MINARA_API_KEY is set, CLI authenticates automatically.
Transaction confirmation (CRITICAL)
For any fund-moving command (swap, transfer, withdraw, perps order, perps deposit, perps withdraw, limit-order create, deposit buy):
Before executing: show the user a summary of what will happen (action, token, amount, recipient/chain) and ask for explicit confirmation. Do NOT auto-confirm.
After the CLI returns a confirmation prompt (e.g. "Are you sure you want to proceed?"): relay the details back to the user and wait for the user to approve before answering y. Never answer y on the user's behalf without their consent.
If the user declines: abort the operation immediately.
This applies to all operations that move funds. Read-only commands (balance, assets, chat, discover, etc.) do not require confirmation.
Intent routing
Match the user's message to the first matching row.
Swap / buy / sell tokens
Triggers: message contains token names/tickers + action words (swap, buy, sell, convert, exchange, trade) + optionally a chain name.
Chain is auto-detected from the token. If a token exists on multiple chains, the CLI prompts the user to pick one (sorted by gas cost). Sell mode supports -a all to sell entire balance.
User intent pattern
Action
"swap 0.1 ETH to USDC", "buy me 100 USDC worth of ETH", "sell 50 SOL for USDC", "convert 200 USDC to BONK on Solana" — natural-language or explicit swap
Triggers: message mentions trending tokens, trending stocks, crypto market sentiment, fear and greed, or Bitcoin metrics.
User intent pattern
Action
"what crypto tokens are trending", "hot tokens right now"
minara discover trending
"what stocks are trending", "trending stocks", "top stocks today"
minara discover trending stocks
"search for SOL tokens", "find crypto token X", "look up AAPL", "search TSLA"
minara discover search <query>
"crypto fear and greed index", "market sentiment"
minara discover fear-greed
"bitcoin on-chain metrics", "BTC hashrate and supply data"
minara discover btc-metrics
Minara premium / subscription
Triggers: message explicitly mentions Minara plan, subscription, credits, or pricing.
User intent pattern
Action
"show Minara plans", "Minara pricing"
minara premium plans
"my Minara subscription status"
minara premium status
"subscribe to Minara", "upgrade Minara plan"
minara premium subscribe
"buy Minara credits"
minara premium buy-credits
"cancel Minara subscription"
minara premium cancel
x402 protocol payment
Triggers: agent receives HTTP 402 Payment Required, or user mentions x402, paid API, or paying for API access with crypto. x402 spec.
Flow: parse PAYMENT-REQUIRED header (amount, token, recipient, chain) → minara balance → minara transfer to pay → retry request.
User intent pattern
Action
Agent receives 402 with x402 headers
Parse headers → minara transfer (USDC to recipient on required chain) → retry
"pay for this API with Minara", "use Minara wallet for x402"
minara balance → minara transfer to service address
"fund my wallet for paid APIs"
minara deposit buy (credit card) or minara deposit spot (crypto)
Minara login / setup
Triggers: message explicitly mentions Minara login, setup, or configuration.
Login: Prefer device code flow (minara login --device) for headless or non-interactive environments; otherwise minara login (interactive).
User intent pattern
Action
"login to Minara", "sign in to Minara", first-time Minara setup
minara login (prefer device code) or minara login --device
"logout from Minara"
minara logout
"configure Minara settings"
minara config
Notes
Token input (-t): accepts $TICKER (e.g. '$BONK'), token name, or contract address. Quote $ in shell.
JSON output: add --json to any command for machine-readable output.
Transaction safety: CLI flow: first confirmation → transaction confirmation (mandatory, shows token + address) → Touch ID (optional, macOS) → execute. Agent must never skip or auto-confirm any step — always relay to user and wait for approval.
Credentials & config
CLI session:~/.minara/credentials.json — auto-created via minara login (required).
API Key:MINARA_API_KEY via env or skills.entries.minara.apiKey in ~/.openclaw/openclaw.json — optional; if set, CLI authenticates automatically without login.