Market Signals
Start-of-chat Trading, Yield, and Prediction signals in Command. Tap a suggestion to ask in chat.
Market Signals is the start-of-chat suggestion surface in Command. Before you type, Console can show Trading, Yield, and Prediction lanes when fresh data is available. Each lane offers prompts you can send with one click.
Open Command at thirdfy.com/console. Market Signals appear when you start a new chat or when the thread has no messages yet.
What each lane shows
| Lane | Source | Examples |
|---|---|---|
| Trading | Trending perps and venue signals | Hyperliquid, Lighter readiness and market prompts |
| Yield | Base USDC earn opportunities | Yield.xyz, Aegis, Morpho, and Curve when present |
| Prediction | Polymarket finance, crypto, and macro | Browse markets by category |
Unavailable lanes are hidden. If no live signals are ready, Command skips this section and keeps the normal prompt chips and composer available.
Featured strategy
The first governed strategy is Base USDC Yield (base-usdc-yield). It appears as a featured card when the yield lane is healthy. Clicking a card or prompt sends the text into Command as a normal message. The operator then loads the right tool packs (earn, prediction, or perps) and answers from live data.
Market Signal cards do not execute trades or deposits by themselves. Writes still require delegation and confirmation in chat.
Automation and EarnClaw
Always-on yield agents live on EarnClaw. Ask in chat when you want to explore automation or deploy a hosted agent. Market Signals cards do not show a separate handoff button.
Deposit prompts
Yield suggestions stay focused on the selected vault, current APY, risk notes, and the next preflight step. They should not introduce hosted agents or automation unless you ask for recurring management.
Pricing
Loading Market Signals and clicking a suggestion is free. The chat turn that follows uses your normal Credits and balance rules: economy free tier, then USD balance. Tool calls inside the turn bill per the action catalog (read_offchain, read_rpc, preflight, write).
Builders: CLI and MCP parity
The underlying API and developer tools still use the Brain namespace:
| Surface | Entry |
|---|---|
| Agent CLI | thirdfy-agent brain sections|suggest|preflight|graduate |
| Thirdfy MCP | brain_sections, brain_suggest_strategy, brain_quote_or_preflight, brain_prepare_earnclaw_handoff |
| HTTP API | GET /api/v1/console/brain-sections, /brain/suggest, /brain/preflight, /brain/graduate |
All Brain routes are read or preflight-first. preflight and graduate require Privy auth.
Related
- Command: Chat, Help Hub, and model picker
- Automations: Scheduled commands on a timer
- Integration paths: Console vs CLI vs MCP