CLI reference

Full reference for every miramarket-cli command. For installation and a first walkthrough, see CLI. For the strategy JSON format and correctness rules, see /agent-strategy-guide.md. Every command supports --json for machine-readable output. In --json mode, stdout carries exactly one JSON object and nothing else — no banners, color, or spinner frames — except strategies watch --events, noted below. Piping to a non-TTY also disables color and spinners automatically.

Envelope and exit codes

Every command that supports --json emits the same envelope shape on both success and failure:

{
  "ok": true,
  "command": "account status",
  "...": "command-specific fields"
}

On failure, ok is false and the envelope also carries a human-readable error and a machine-readable code:

{
  "ok": false,
  "command": "post",
  "error": "Not authenticated. Run `miramarket-cli login` first.",
  "code": "NOT_AUTHENTICATED"
}

Prefer branching on code over parsing error text — error wording can change, code is the stable contract.

Exit code	Meaning
0	Success
1	Generic / unexpected failure
2	Validation failure
3	Authentication failure (not signed in, expired token)
4	Server failure (upstream error, geo-restricted, timeout)
5	Bad input (missing file, malformed JSON, missing/invalid flags)

code values include NOT_AUTHENTICATED, VALIDATION_ERROR, INPUT_ERROR, SERVER_ERROR, PARSE_ERROR, STRATEGY_NOT_FOUND, REGION_RESTRICTED, WALLET_NOT_DELEGATED, WATCH_TIMEOUT, INVALID_STRATEGY_STATE, NO_ACTIVE_RUN, LOCKED_NODE_EDIT, UNSUPPORTED_FIELD, RUN_EDIT_REJECTED, and more — this set grows over time, so don’t treat it as closed. Authenticates via an OAuth device flow: prints a short code and a verification link, you approve it in any browser (doesn’t need to be the same device — useful over SSH or on a headless machine), and the CLI finishes automatically once approved. A valid cached session short-circuits this by default; pass --force to sign in again (for example, to switch accounts). Signing in starts a session but does not by itself make the account trade-ready — see account setup under Account commands below.

`miramarket-cli logout`

Clears the cached session on this machine.

`miramarket-cli auth status [--json]`

Reports whether a valid session is cached. Always exits 0 — this is a diagnostic, read the payload:

{
  "ok": true,
  "command": "auth status",
  "authenticated": true,
  "postingAllowed": true,
  "did": "did:privy:...",
  "expiresAt": "2026-05-09T12:00:00.000Z"
}

Account commands

A signed-in session is not the same as a trade-ready account — Polymarket orders and live strategy runs also require accepting the platform’s Terms/Privacy/Risk Disclosure and having a delegated deposit wallet with the necessary on-chain approvals.

`miramarket-cli account status [--json]`

Diagnoses trade-readiness across auth, API reachability, region availability, policy acceptance, wallet delegation, and capital. Always exits 0 — ok:true means “the check ran,” not “everything passed.” Read ready and blockers[]:

{
  "ok": true,
  "command": "account status",
  "ready": false,
  "blockers": [
    {
      "code": "POLICIES_NOT_ACCEPTED",
      "message": "You have not accepted the current Terms, Privacy Policy, and Risk Disclosure.",
      "requiredAction": "A human must run `miramarket-cli account accept-policies` in an interactive terminal.",
      "humanRequired": true
    }
  ],
  "checks": {
    "auth": { "ok": true, "did": "did:privy:...", "expiresAt": "..." },
    "api": { "ok": true },
    "geo": { "ok": true, "country": "GB" },
    "policies": { "ok": false, "accepted": false },
    "wallet": { "ok": true, "delegated": true, "depositWalletAddress": "0x..." },
    "capital": { "ok": true, "cashAtomic": 50000000 }
  }
}

If humanRequired is true on a blocker (not authenticated, wallet not delegated, policies not accepted, region-restricted), surface requiredAction and stop — an agent should never attempt to work around these. Blocker codes: NOT_AUTHENTICATED, API_UNREACHABLE, REGION_RESTRICTED, POLICIES_NOT_ACCEPTED, WALLET_NOT_DELEGATED, WALLET_CHECK_FAILED.

`miramarket-cli account setup [--json]`

Idempotent — attaches the wallet-level policy and bootstraps the deposit wallet’s on-chain approvals; safe to re-run any time. Cannot complete onboarding by itself: wallet delegation only happens in a browser during sign-in, and this command never accepts policies on your behalf. It reports exactly what’s still needed and points at account accept-policies or a browser sign-in.

`miramarket-cli account policies [--json]`

Read-only. Shows the current Terms/Privacy/Risk Disclosure versions, your acceptance status, and canonical URLs.

`miramarket-cli account accept-policies`

Records legal acceptance of the current Terms, Privacy Policy, and Risk Disclosure. This is a human-only action — it requires typing I accept in an interactive terminal (or, for a human scripting their own machine, pinning the exact current document versions with --i-have-read-and-accept --terms-version=... --privacy-version=... --risk-version=...). An AI agent should never call this on a user’s behalf.

`miramarket-cli account capital [--json]`

Shows capital currently locked by active strategy runs and pending withdrawal holds — the gap between gross wallet balance and what’s actually spendable.

`miramarket-cli account withdraw --recipient <address> [--amount <usd>] --confirm [--json]`

Withdraws spendable USDC to an external address. Omit --amount to withdraw all spendable cash. Requesting more than spendable cash is rejected before anything is moved.

miramarket-cli account withdraw --recipient 0xabc... --amount 25 --confirm --json

Exit codes: 0 ok, 3 auth error, 4 server error (a failed transfer releases its hold automatically), 5 bad input.

Strategy authoring commands

See /agent-strategy-guide.md for the JSON format itself and the rules for building a strategy that behaves correctly, not just one that passes validate.

`miramarket-cli schema [--format=ts|json|markdown]`

Prints the strategy schema — ts for TypeScript types, json for a JSON Schema document, markdown for a prose authoring guide with worked examples.

`miramarket-cli strategies generate [prompt] [flags]`

Text-to-strategy. Describe what the strategy should do in plain English and get authoring JSON back, built by the same assistant that powers the visual builder. Requires authentication. Nothing is validated or posted on your behalf: run validate, preview, and post on the result exactly as you would for a hand-written file.

Flag	Description
`--out <file>`	Write the strategy JSON here. Without it the strategy is embedded in the result as `strategy`.
`--strategy <file>`	Edit an existing local strategy file instead of building from scratch: the prompt is applied as a change to it, and `changeSummary` lists what changed.
`--choose <marketId\|n>`	Answer the market question from the previous call (see below): a candidate’s market id, or its number as printed. Do not pass a prompt with it.
`--selection <id>`	With `--choose`: the `selectionId` the question came with, so a question asked by another session in the meantime is refused rather than answered.

result is one of four values. ok is true for all of them, because each is a real outcome rather than a failure:

strategy — built. strategyPath or strategy, plus markets[] (what it trades, with the price the generator saw), stats, notices[], unmatched[], changeSummary[] (edits only), and nextCommands[]. A non-empty unmatched means something the prompt named was substituted or left out; read it before posting. A tokenized stock comes back as a BASE_STOCKS leg with PRICE_USD conditions in dollars, ready to post.
market_selection — the request was ambiguous between several markets. candidates[] is numbered (choice) and the question is saved locally under selectionId. When resumable is true, answer with strategies generate --choose <marketId|choice> --selection <selectionId> on the next call; at an interactive terminal the choice is prompted for in place instead. When resumable is false the question cannot be answered with a choice (the request was an edit, or it named several markets) and reason says so; re-run with a prompt that names the market precisely. Any new prompt discards the saved question.
clarification — nothing was built; question says what is missing. Re-run with a prompt that answers it.
answer — the prompt was a question rather than a build request; answer is the reply.

miramarket-cli strategies generate "buy YES on the Fed cutting rates in December if it drops below 40c, sell at 70c" --out ./fed.json --json
miramarket-cli strategies generate "buy TSLA if it crosses \$400, sell at \$450" --out ./tsla.json --json
miramarket-cli strategies generate "also sell everything if it drops below 30c" --strategy ./fed.json --out ./fed.json --json
miramarket-cli strategies generate --choose 3215006 --selection a1b2c3d4 --out ./fed.json --json

{
  "ok": true,
  "command": "strategies generate",
  "prompt": "buy TSLA if it crosses $400, sell at $450",
  "result": "strategy",
  "strategyPath": "./tsla.json",
  "edited": false,
  "markets": [
    { "market_id": "0xb2000000000000000000001e800a7f5189430cD0", "title": "Tesla Inc. (TSLAc)", "venue": "BASE_STOCKS", "outcome": "LONG", "current_price": 355.69 }
  ],
  "stats": { "actionCount": 2, "conditionCount": 2, "riskProfile": "BALANCED", "heuristicScore": 90 },
  "notices": [],
  "unmatched": [],
  "changeSummary": [],
  "nextCommands": [
    "miramarket-cli validate ./tsla.json --json",
    "miramarket-cli preview ./tsla.json --json",
    "miramarket-cli post ./tsla.json --demo --json"
  ]
}

Exit codes: 0 for every result, 3 auth error, 4 generation failed, 5 bad input (code says which).

`miramarket-cli validate <file> [--json]`

Validates a strategy JSON file’s structure. Exit 0 valid, 2 validation errors, 5 bad input (missing file, malformed JSON).

{
  "ok": true,
  "command": "validate",
  "strategyPath": "./my-strategy.json",
  "valid": true,
  "errors": [],
  "warnings": []
}

`miramarket-cli preview <file> [--json]`

Summarizes a strategy without contacting the server — node/edge counts, required principal, and warnings[] for anything that will be silently dropped or misbehave at import.

`miramarket-cli edit <file> [flags]`

Updates fields in a local strategy JSON file. Edits apply in memory and the result is fully re-validated before writing — if validation fails, the source file is left untouched and the output reports the errors. edit never contacts the server; to change a strategy you have already posted, use strategies pull and strategies update.

Flag	Description
`--set <path>=<value>`	Set a field (repeatable). Value is parsed as JSON, falling back to string.
`--unset <path>`	Remove a field (repeatable).
`--out <path>`	Write to a different output file.
`--demo` / `--no-demo`	Write or remove `is_demo: true`.

miramarket-cli edit ./strategy.json --set initial_principal_usd=100
miramarket-cli edit ./strategy.json --set "nodes[0].condition.threshold=0.7"
miramarket-cli edit ./strategy.json --unset nodes[1].action.risk_guards

`miramarket-cli post <file> [flags]`

Validates and posts a strategy, then starts a run (unless --no-start). A live (non-demo) post runs a Polymarket market-health check first; demo posts skip it.

Flag	Description
`--no-start`	Import only, don’t start a run.
`--name <name>`	Override the strategy name (defaults to its `strategy_id`).
`--demo`	Post as a simulation — no real orders placed.
`--skip-health-check`	Demo runs only; rejected outright on a live strategy.

{
  "ok": true,
  "command": "post",
  "posted": true,
  "started": true,
  "strategyId": "k97abc123...",
  "runId": "k97xyz456...",
  "name": "eth-momentum-v1",
  "demo": false
}

Exit codes: 0 ok, 2 validation error, 3 auth error, 4 server error, 5 bad input.

Market data commands

None of these require authentication.

Command	What it does
`markets list [--limit <n>] [--offset <n>]`	Lists Polymarket events by id, title, volume.
`markets search <query> [--limit <n>]`	Searches events by keyword, sorted by relevance.
`markets show <eventId>`	Full event detail: description, end date, volume, liquidity, and each sub-market’s outcome prices and CLOB token IDs.
`markets orderbook <tokenId> [--depth <n>]`	Live top bids/asks for a CLOB token.
`markets prices-history <market> [--interval <interval>]`	Price history; `--interval` is one of `1h`, `6h`, `1d`, `1w`, `1m`, `max`.

{
  "ok": true,
  "command": "markets show",
  "id": "abc123",
  "title": "Will X happen?",
  "markets": [
    { "id": "...", "question": "...", "outcomePrices": ["0.62", "0.38"], "clobTokenIds": ["...", "..."] }
  ]
}

Tokenized stock commands

Tokenized stocks on Base (AAPLc, TSLAc, NVDAc, and others) are real equities wrapped as tokens. They are not prediction markets: a strategy buys and sells them as token swaps, and a condition watches them by share price in dollars. markets search never finds them, so these commands exist instead. None require authentication.

Command	What it does
`stocks list`	Every tradable stock with its live pool price. `priced` says how many rows have a usable price; an unpriced row is still listed, just not sizable right now.
`stocks show <stock>`	One stock, with the exact `actionTarget` block to paste into an ACTION node. Accepts a ticker (`TSLA`), token symbol (`TSLAc`), company name (`Tesla`), or contract address.
`stocks history <stock> [--range 1D\|1W\|1M\|ALL]`	Pool price history, oldest bar first. `1D` is 15-minute bars, `1W` (default) hourly, `1M` 4-hourly, `ALL` daily.

{
  "ok": true,
  "command": "stocks show",
  "symbol": "TSLAc",
  "ticker": "TSLA",
  "name": "Tesla Inc.",
  "address": "0xb2000000000000000000001e800a7f5189430cD0",
  "priceUsd": 356.47,
  "oraclePriceUsd": 353.33,
  "poolPremiumBps": 89,
  "actionTarget": {
    "venue": "BASE_STOCKS",
    "market": { "market_id": "0xb2000000000000000000001e800a7f5189430cD0", "outcome_token": "LONG", "token_id": "0xb2000000000000000000001e800a7f5189430cD0" }
  },
  "conditionSupported": true,
  "conditionSignal": "PRICE_USD"
}

Two prices appear, and they mean different things. priceUsd is the pool price, what a swap actually pays, and what a position is sized from. oraclePriceUsd is the reference price of the underlying share, what a PRICE_USD condition watches; the gap between them is poolPremiumBps. Both are dollars per share, never a 0–1 probability. A large oracleAgeSeconds outside US market hours is expected, not a fault.

{
  "ok": true,
  "command": "stocks history",
  "ticker": "TSLA",
  "range": "1W",
  "priceSource": "aerodrome_pool",
  "unit": "USD per token",
  "stale": false,
  "count": 168,
  "firstPriceUsd": 351.12,
  "lastPriceUsd": 356.47,
  "changePct": 1.52,
  "points": [{ "t": 1790000000, "p": 351.12 }, { "t": 1790003600, "p": 351.9 }]
}

stocks history charts the pool price (priceSource names it), not the reference price. stale: true means fresh history was unavailable and the last good reading was returned. stocks show and stocks history exit 5 for a company that is not in the registry, and, distinctly, for one that is listed but has no pool to trade in yet (COINc, CRCLc, INTCc). portfolio reports stock holdings separately from cash (stockPositions, stockValueUsd), because a share has to be sold before a strategy can spend the proceeds. Tokenized stocks are geo-restricted: where they are not offered, posting a live strategy that buys one is refused with “Tokenized stocks are not available in your region”. account status --json shows the region check under checks.geo.

Trading and portfolio commands

`miramarket-cli trade [flags]`

Places a CLOB limit order directly — for manual/tactical orders, not strategy automation (use post under Strategy authoring commands for that). Requires authentication and --confirm.

Flag	Required	Description
`--token-id`	yes	CLOB token ID for the outcome you’re trading.
`--side`	yes	`buy` or `sell`.
`--price`	yes	Limit price between 0 and 1 (e.g. `0.55` = 55¢).
`--size`	yes	Order size in USDC.
`--order-type`	no	`FOK` (fill-or-kill, default) or `GTC` (rests on the book).
`--confirm`	yes	Required safety flag.

miramarket-cli trade --token-id 2174263... --side buy --price 0.55 --size 10 --confirm --json

Exit codes: 0 ok, 3 auth error, 4 server error, 5 bad input.

Command	What it does
`order status [orderId]`	Status of one order, or all open orders if omitted.
`order cancel <orderId> --confirm`	Cancels an open GTC order.
`balance [--chain base\|polygon\|all]`	USDC balance per chain, plus `cash` (gross minus locked/pending).
`portfolio [--venue polymarket\|base-stocks\|all]`	Balances, open orders, settled positions, tokenized stock holdings, capital reservations.

Strategy management commands

Command	What it does
`strategies generate [prompt] [--out <file>]`	Build a strategy from a plain-English description — see Strategy authoring commands.
`strategies list`	Every strategy you own, with status and latest run info.
`strategies show <strategyId> [--verbose]`	Detail for one strategy; `--verbose` adds per-node PnL, executed trades, and settlement detail.
`strategies runs <strategyId> [--limit <n>]`	Run history, most recent first.
`strategies watch <strategyId> [flags]`	Polls until the run reaches a terminal status — see below.
`strategies rename <strategyId> <name>`	Rename (1–120 characters).
`strategies pull <strategyId> [--out <file>]`	Download a posted strategy as authoring JSON, with the node keys its active run has locked — see below.
`strategies update <strategyId> [file] [--set ...] [--unset ...]`	Change the future part of a running strategy in place — see below.
`strategies cancel <runId>`	Cancel an active run.
`strategies exit <strategyId>`	Close a completed strategy, freeing its locked principal.
`strategies delete <strategyId> --confirm`	Permanently delete a draft strategy (never started).

`strategies watch <strategyId> [flags]`

Flag	Description
`--json`	Blocks, emits exactly one final envelope on completion.
`--events`	Emits one NDJSON line per status transition, then a final line — the one exception to “one JSON object per command.”
`--run <runId>`	Watch a specific run instead of the strategy’s latest.
`--until <statuses>`	Comma-separated terminal statuses to stop at (default `completed,failed,canceled`).
`--timeout <seconds>`	Give up after this long (default 86400); exits `4` with `WATCH_TIMEOUT`.
`--interval <seconds>`	Poll interval (default 5).
`--fail-on-error`	Exit `4` if the run itself ends `failed`/`canceled` (default: the watch succeeding is exit `0` regardless of run outcome).

miramarket-cli strategies watch <strategyId> --events --timeout 600

Editing a running strategy

strategies pull and strategies update round-trip a strategy that is already running. Only the future part of the graph can change: nodes the run has executed or is waiting on are locked, and so are root_node_id and initial_principal_usd. Drafts and finished strategies cannot be edited in place — post a new strategy instead.

`strategies pull <strategyId> [--out <file>] [--json]`

Writes the strategy as authoring JSON (embedded in the envelope, or to --out) and reports which nodes you may touch:

Field	Meaning
`editable`	`true` only while a run is active.
`lockedNodeKeys`	Nodes you must leave exactly as pulled.
`hardLockedNodeKeys`	Executed and in-flight actions: no field or edge changes.
`waitingConditionKeys`	Conditions the run is waiting on: their own settings and existing branches are fixed, but they may fan out a new sibling action.
`editableNodeKeys`	Everything downstream.

Nodes keep their node_id across the round trip, so nodes[i] positions from pull are stable for --set.

`strategies update <strategyId> [file] [--set <path>=<value>] [--unset <path>] [--json]`

Uploads either a file (usually one written by pull --out) or the posted graph with dot-path edits applied directly, then saves it. Before anything is sent, the CLI checks the locks and validates the result; the server repeats the checks and additionally rejects edges rewired into the executed past.

Outcome	Exit	`code`
A locked node, the root, or the principal changed	5	`LOCKED_NODE_EDIT`
The edit only touches fields the server does not persist (`risk_guards`, `stabilizers`, `market_selector`)	5	`UNSUPPORTED_FIELD`
The strategy has no active run	5	`NO_ACTIVE_RUN`
The edited graph fails validation	2	`VALIDATION_ERROR`
The server refused the graph (for example an edge rewired into the past)	5	`RUN_EDIT_REJECTED`

An ABSOLUTE_TIME condition whose trigger time has already passed is accepted only if you leave it, its decision group, and the actions it gates exactly as pulled; change anything it gates and you must also give it a future time.

# Pull, edit the file, push it back
miramarket-cli strategies pull <strategyId> --out ./strategy.json --json
miramarket-cli strategies update <strategyId> ./strategy.json --json

# Or edit the posted graph directly
miramarket-cli strategies update <strategyId> --set "nodes[4].condition.threshold=0.35" --json

Bridging commands

Move USDC between Base and Polygon, or swap Polygon USDC to USDC.e, before trading. All require authentication (the wallet address is resolved from your session).

Command	Description
`bridge quote --amount <usd> --direction <direction>`	Get a 0x quote. Returns `quoteId`, `transactions[]`, `expectedInputAmount`, `expectedOutputAmount`, `isCrossChain`.
`bridge execute --amount <usd> --direction <direction> --confirm [--no-wait]`	Execute the transfer. Returns `quoteId`, `txHash` (the origin transaction), `txHashes[]`, `chainId`, and either `bridgeStatus` (cross-chain) or `settled` (same-chain swap).
`bridge status <txHash> --chain-id <8453\|137> [--quote-id <id>]`	Poll a cross-chain transfer by its origin transaction hash (no auth required). `status` is one of `origin_tx_pending`, `origin_tx_succeeded`, `origin_tx_confirmed`, `origin_tx_reverted`, `bridge_pending`, `bridge_filled`, `bridge_failed`, `unknown`.

--direction is one of base-to-polygon, polygon-to-base, polygon-usdc-to-usdce, polygon-usdce-to-usdc. The last two are same-chain swaps on Polygon, which have no bridge to poll. By default bridge execute waits: ok: true means a cross-chain transfer filled, or a same-chain swap confirmed on-chain. It exits 4 in three cases, and none of them is a reason to run bridge execute again, because the transaction is already on-chain and a retry would move the funds a second time:

BRIDGE_FAILED: the cross-chain bridge failed. The envelope says whether the funds were refunded on the origin chain.
BRIDGE_PENDING: the cross-chain transfer is still in flight after the polling window. Poll it with bridge status <txHash> --chain-id <chainId> using the values in the envelope.
SWAP_UNCONFIRMED: a same-chain swap on Polygon was submitted but not confirmed within the wait window. There is no bridge to poll. Look up the txHash from the envelope on a Polygon block explorer, or run balance --chain polygon until the USDC and USDC.e balances reflect the swap.

miramarket-cli bridge quote --amount 100 --direction base-to-polygon --json
miramarket-cli bridge execute --amount 100 --direction base-to-polygon --confirm --json
miramarket-cli bridge status 0xabc... --chain-id 8453 --json

A strategy funds itself. Posting one that needs USDC on the other chain bridges on demand, so a manual bridge is only for moving funds ahead of time or for withdrawing.

`miramarket-cli status`

Shows local CLI state: auth, last strategy worked on, last post result, remaining required actions.

Environment variables

Variable	Effect
`NO_COLOR`	Disables ANSI color (follows no-color.org).
`MIRAMARKET_API_URL`	Override the API base URL (default `https://api.miramarket.org`).
`MIRAMARKET_CONVEX_URL`	Override the Convex deployment URL.
`MIRAMARKET_WEB_URL`	Override the strategy-builder web app URL used by `login`’s browser step (default `https://app.miramarket.org`).
`MIRAMARKET_CONFIG_DIR`	Override where the cached session and local state live (default `~/.config/miramarket-cli`).

Session lifetime

The cached access token lasts 15 minutes, but the CLI also caches a 30-day refresh token (rotated on every use) and silently redeems it at the start of every command — there’s no re-login to babysit, on a laptop or an unattended server alike. If the refresh token itself expires or is revoked, the next command reports NOT_AUTHENTICATED and you run miramarket-cli login again.

Get started

Reference

Envelope and exit codes

`miramarket-cli logout`

`miramarket-cli auth status [--json]`

Account commands

`miramarket-cli account status [--json]`

`miramarket-cli account setup [--json]`

`miramarket-cli account policies [--json]`

`miramarket-cli account accept-policies`

`miramarket-cli account capital [--json]`

`miramarket-cli account withdraw --recipient <address> [--amount <usd>] --confirm [--json]`

Strategy authoring commands

`miramarket-cli schema [--format=ts|json|markdown]`

`miramarket-cli strategies generate [prompt] [flags]`

`miramarket-cli validate <file> [--json]`

`miramarket-cli preview <file> [--json]`

`miramarket-cli edit <file> [flags]`

`miramarket-cli post <file> [flags]`

Market data commands

Tokenized stock commands

Trading and portfolio commands

`miramarket-cli trade [flags]`

Strategy management commands

`strategies watch <strategyId> [flags]`

Editing a running strategy

`strategies pull <strategyId> [--out <file>] [--json]`

`strategies update <strategyId> [file] [--set <path>=<value>] [--unset <path>] [--json]`

Bridging commands

`miramarket-cli status`

Environment variables

Session lifetime

​Envelope and exit codes

​Sign-in commands

​miramarket-cli login [--force]

​miramarket-cli logout

​miramarket-cli auth status [--json]

​Account commands

​miramarket-cli account status [--json]

​miramarket-cli account setup [--json]

​miramarket-cli account policies [--json]

​miramarket-cli account accept-policies

​miramarket-cli account capital [--json]

​miramarket-cli account withdraw --recipient <address> [--amount <usd>] --confirm [--json]

​Strategy authoring commands

​miramarket-cli schema [--format=ts|json|markdown]

​miramarket-cli strategies generate [prompt] [flags]

​miramarket-cli validate <file> [--json]

​miramarket-cli preview <file> [--json]

​miramarket-cli edit <file> [flags]

​miramarket-cli post <file> [flags]

​Market data commands

​Tokenized stock commands

​Trading and portfolio commands

​miramarket-cli trade [flags]

​Strategy management commands

​strategies watch <strategyId> [flags]

​Editing a running strategy

​strategies pull <strategyId> [--out <file>] [--json]

​strategies update <strategyId> [file] [--set <path>=<value>] [--unset <path>] [--json]

​Bridging commands

​miramarket-cli status

​Environment variables

​Session lifetime

Envelope and exit codes

Sign-in commands

`miramarket-cli login [--force]`

`miramarket-cli logout`

`miramarket-cli auth status [--json]`

Account commands

`miramarket-cli account status [--json]`

`miramarket-cli account setup [--json]`

`miramarket-cli account policies [--json]`

`miramarket-cli account accept-policies`

`miramarket-cli account capital [--json]`

`miramarket-cli account withdraw --recipient <address> [--amount <usd>] --confirm [--json]`

Strategy authoring commands

`miramarket-cli schema [--format=ts|json|markdown]`

`miramarket-cli strategies generate [prompt] [flags]`

`miramarket-cli validate <file> [--json]`

`miramarket-cli preview <file> [--json]`

`miramarket-cli edit <file> [flags]`

`miramarket-cli post <file> [flags]`

Market data commands

Tokenized stock commands

Trading and portfolio commands

`miramarket-cli trade [flags]`

Strategy management commands

`strategies watch <strategyId> [flags]`

Editing a running strategy

`strategies pull <strategyId> [--out <file>] [--json]`

`strategies update <strategyId> [file] [--set <path>=<value>] [--unset <path>] [--json]`

Bridging commands

`miramarket-cli status`

Environment variables

Session lifetime