Myriad CLI

Build AI trading agents on Myriad prediction markets in minutes.

Myriad CLI gives one interface for the full loop: discover markets, make decisions, execute trades, and claim winnings, with MCP support out of the box.

What You Can Build

• Discover live opportunities across open markets using sorting and keyword search.
• Decide with fast market inspection and portfolio context.
• Execute buys and sells.
• Claim winnings.
• Automate the full workflow through MCP tool orchestration.

Start in seconds

Install (requires Node.js and npm):

npm i -g @myriadmarkets/cli

If myriad is not found immediately after install, open a new terminal session.

Set up a signer wallet (create or import from private key or seedphrase, interactive only):

myriad wallet setup

Fund your wallet for trading:

myriad wallet deposit

Find markets:

myriad markets list --state open --order volume --sort desc --limit 5 --json

Buy a position:

myriad trade buy --market-id 164 --outcome-id 0 --value 25 --json

Use the --dry-run flag to preview trades without executing them.

Run as MCP server:

myriad mcp

Use cases

1) Event-Driven Trader Agent

Your agent spots a news catalyst, scans markets, and stages a trade.

myriad markets list --state open --keyword election --limit 10 --json
myriad trade buy --market-id 164 --outcome-id 0 --value 25 --dry-run --json

Go deeper:

• Market discovery skill
• Trade execution skill

2) Portfolio Monitor Agent

Your agent checks exposure, cash, and gas before every trading cycle.

myriad wallet balances --json
myriad wallet deposit --json
myriad portfolio --limit 20 --json

Go deeper:

• Wallet ops skill
• Market discovery skill

3) Winnings sweeper agent

Your agent regularly sweeps resolved positions and claims winnings.

myriad claim all --dry-run --json
myriad claim all --json

Go deeper:

• Claims skill

4) Multi-Agent Trading Desk (MCP)

One scout agent reads markets, another agent trades.

myriad mcp

Go deeper:

• MCP orchestration skill

MCP in One Minute

MCP client config:

{
  "mcpServers": {
    "myriad": {
      "command": "myriad",
      "args": ["mcp"]
    }
  }
}

Safe rule for every agent:

1. Use read tools first (markets_*, portfolio, wallet_balances).
2. Use dryRun: true first for write tools (trade_*, swap_stable, claim_*).
3. Execute without dryRun only after validation.

Command Map

Core command groups: markets -> trade -> claim -> wallet -> swap -> skills -> mcp

Skills

| Skill | Owns | | --- | --- | | myriad-market-discovery | Market scanning, filtering, and candidate selection | | myriad-trade-execution | Buy/sell execution patterns, slippage and allowance strategy | | myriad-claims | Winnings, voided claims, and claim-all workflows | | myriad-wallet-ops | Wallet onboarding, signer resolution, keychain issues | | myriad-mcp-orchestration | MCP sequencing, safety rules, and per-call override behavior |

Agent Platform Setup

Claude Code

Install skills into your project:

myriad skills install --target claude

This copies skills to .claude/skills/ in the current directory. You can then invoke them with /myriad-market-discovery, /myriad-trade-execution, etc.

To use Myriad as an MCP server, add to your Claude Code MCP config:

{
  "mcpServers": {
    "myriad": {
      "command": "myriad",
      "args": ["mcp"]
    }
  }
}

OpenClaw

Install skills globally:

myriad skills install --target openclaw

This copies skills to ~/.openclaw/skills/ where OpenClaw auto-discovers them. Each skill requires the myriad binary on PATH.

Install Both

myriad skills install

Use --force to overwrite existing skill files.

Defaults and Risk (Read Once)

• Plain ASCII tables are the default output mode.
• Pass --json to output JSON instead.
• In markets list --plain, output columns are: Title, Most likely outcome (with price), Volume, Expires At, State, Market ID.
• In markets show --plain, output columns are: Title, Outcome (Price), Outcome (Price), Volume, Expires At, Market ID.
• In markets list --plain, outcome prices and volumes are USD currency-formatted; Expires At is date-only, HIT for >= 2100-01-01, and Perpetual when perpetual is true.
• In portfolio --plain, rows are filtered to unclaimed open/voided/won positions and shown as Market, Outcome, Shares, Price, Current Value, Current ROI, Status, Market ID, Outcome ID.
• In wallet deposit --plain, output is instruction text lines (not an ASCII table).
• If both --json and --plain are passed, --json takes precedence.
• Default chain is BNB Chain (chainId=56).
• Default API base URL is https://api-v2.myriadprotocol.com/.
• Default slippage: trades 0.05, stable swaps 0.005.
• On BNB Chain, buy flow can auto-swap USDT/USD1 if required spend token balance is insufficient.
• Light risk note: prediction market execution is probabilistic and market conditions can change quickly; use dry-runs before writing transactions.

Configuration Layers

Myriad CLI resolves config values in this order:

1. CLI flags (for example --rpc-url, --chain-id, --allowance).
2. Environment variables (MYRIAD_*) and .env in the current working directory.
3. Global machine config file:

• $XDG_CONFIG_HOME/myriad/config.json when XDG_CONFIG_HOME is set.
• Otherwise ~/.config/myriad/config.json.

4. Built-in network defaults.

Supported global config keys: apiBaseUrl, apiKey, allowance, chainId, rpcUrl, predictionMarketAddress, predictionMarketQuerierAddress, collateralTokenAddress, usdtTokenAddress, usd1TokenAddress, pancakeRouterV2Address.

Example global config:

{
  "chainId": 56,
  "rpcUrl": "https://bsc-dataseed.binance.org/",
  "apiBaseUrl": "https://api-v2.myriadprotocol.com/",
  "apiKey": "optional-api-key",
  "allowance": "UNLIMITED"
}

Security note:

• Do not place private keys in global config.
• Use myriad wallet setup (encrypted wallet file + OS keychain), MYRIAD_PRIVATE_KEY, or --private-key.

Further Reading

• Myriad API v2 reference
• .env defaults
• All Myriad skills