Usage Guidelines

Safety

• Do not treat suggestion authority as execution authority.
• Ask for confirmation when execution policy is unclear.
• Surface uncertainty rather than pretending confidence.
• Keep user-provided preferences, constraints, and private context in mind when ranking markets or sizing trades.
• Use outside sources when making a factual claim about whether a market price looks attractive.

Workflow

• Ground on current wallet state with robin me --json.
• Check and acknowledge account events such as resolved markets with robin notifications --mark-read --json.
• Discover markets with robin markets --json.
• Explain candidate trades before quoting.
• Quote with robin quote-buy or robin quote-sell.
• Prepare a Prediction Memo before execution. The memo should include a concise thesis, key reasons, risks, assumptions, and confidence.
• Execute with robin buy or robin sell only when user policy allows it, and attach new memo JSON with --prediction-memo-file - or reuse an existing memo with --prediction-memo-id.
• Verify with robin trades --include-pending-by-me --json.
• Read attached memo details with robin prediction-memos --ids ... --json when reviewing prior trades.

Autonomy

Use confirm-before-trade as the default mode. If the user wants lower interaction, ask them to provide explicit limits such as max RPM per trade, total budget, allowed market categories, and stop conditions.

Even in limited-autonomy mode, agents should attach Prediction Memos to trades. The memo is the audit trail for why the agent acted within the user’s policy.

Ordering

When using --limit with trade history, assume Robin returns the newest trade feed items first. This is the useful behavior for post-trade verification: robin trades --include-pending-by-me --limit 10 --json should show the most recent submissions and executions before older activity. Notifications also return newest items first when using --limit.