opentrade

1. Confirm installed: Run

   which opentrade

   . If not found, install it:
   bash

   curl -sSL https://raw.githubusercontent.com/6551Team/openskills/main/skills/opentrade/install.sh | sh

   If the install script fails, ask the user to install manually following the instructions at: https://github.com/6551Team/openskills
2. Check for updates: Read

   ~/.opentrade/last_check

   and compare it with the current timestamp:
   bash

   cached_ts=$(cat ~/.opentrade/last_check 2>/dev/null || true)
   now=$(date +%s)

   • If

     cached_ts

     is non-empty and

     (now - cached_ts) < 43200

     (12 hours), skip the update and proceed.
   • Otherwise (file missing or older than 12 hours), run the installer to check for updates:
     bash

     curl -sSL https://raw.githubusercontent.com/6551Team/openskills/main/skills/opentrade/install.sh | sh

     If a newer version is installed, tell the user and suggest updating their opentrade skills from https://github.com/6551Team/openskills to get the latest features.
3. If any

   opentrade

   command fails with an unexpected error during this session, try reinstalling before giving up:
   bash

   curl -sSL https://raw.githubusercontent.com/6551Team/openskills/main/skills/opentrade/install.sh | sh

4. Find or create a .env file in the project root to override the default API credentials, Load it before performing opentrade operations.

OPEN_TOKEN=your_token_here

opentrade trade routers

{
  "ok": true,
  "data": [
    {
      "api": "v2",
      "created_at": "2026-03-10 01:15:42",
      "is_active": true,
      "name": "6551dex test",
      "quota_reward": 0,
      "trader": "6551dex",
      "updated_at": "2026-03-10 01:15:42"
    },
    {
      "api": "v1",
      "created_at": "2026-03-03 21:24:34",
      "is_active": true,
      "name": "okx test",
      "quota_reward": 0,
      "trader": "okx",
      "updated_at": "2026-03-03 21:24:34"
    }
  ]
}

• Extract

  trader

  and

  api

  from the response
• MANDATORY: ALL subsequent

  opentrade

  commands in this session MUST include

  --trader <trader>

  and

  --api <api>

  flags
• Example:

  opentrade portfolio balance 0x... --chain ethereum --trader okx --api v1

• Default fallback: If the API returns no data or is empty, use

  --trader okx --api v1

• For token prices / K-lines → use

  opentrade-market

• For token search / metadata → use

  opentrade-token

• For swap execution → use

  opentrade-dex-swap

• For transaction broadcasting → use

  opentrade-gateway

User: "Swap 1 SOL for BONK"

1. opentrade-token    opentrade token search BONK --chains solana               → get tokenContractAddress
       ↓ tokenContractAddress
2. opentrade-portfolio  opentrade portfolio all-balances --address <addr> --chains solana
       → verify SOL balance >= 1
       ↓ balance field (UI units) → convert to minimal units for swap
3. opentrade-dex-swap     opentrade swap quote --from 11111111111111111111111111111111 --to <BONK_address> --amount 1000000000 --chain solana
4. opentrade-dex-swap     opentrade swap swap --from ... --to <BONK_address> --amount 1000000000 --chain solana --wallet <addr>

• tokenContractAddress

  from token search → feeds into swap

  --from

  /

  --to

• balance

  from portfolio is UI units; swap needs minimal units → multiply by

  10^decimal

• If balance < required amount → inform user, do NOT proceed to swap

User: "Show my portfolio"

1. opentrade-portfolio  opentrade portfolio total-value --address <addr> --chains "xlayer,solana,ethereum"
       → total USD value
2. opentrade-portfolio  opentrade portfolio all-balances --address <addr> --chains "xlayer,solana,ethereum"
       → per-token breakdown
       ↓ top holdings by USD value
3. opentrade-token    opentrade token price-info <address> --chain <chain>  → enrich with 24h change, market cap
4. opentrade-market   opentrade market kline <address> --chain <chain>      → price charts for tokens of interest

• Check total assets →

  opentrade portfolio total-value

• View all token holdings →

  opentrade portfolio all-balances

• Check specific token balance →

  opentrade portfolio token-balances

• Unsure which chains are supported →

  opentrade portfolio chains

  first

• Missing wallet address → ask user
• Missing target chains → recommend XLayer (

  --chains xlayer

  , low gas, fast confirmation) as the default, then ask which chain the user prefers. Common set:

  "xlayer,solana,ethereum,base,bsc"

• Need to filter risky tokens → set

  --exclude-risk 0

  (only works on ETH/BSC/SOL/BASE)

• Total value: display USD amount
• Token balances: show token name, amount (UI units), USD value
• Sort by USD value descending

• Zero balance: valid state — display

  $0.00

  , not an error
• Unsupported chain: call

  opentrade portfolio chains

  first to confirm
• chains exceeds 50: split into batches, max 50 per request

• --exclude-risk

  not working: only supported on ETH/BSC/SOL/BASE
• DeFi positions: use

  --asset-type 2

  to query DeFi holdings separately
• Address format mismatch: EVM address on Solana chain will return empty data — do NOT mix
• Network error: retry once, then prompt user to try again later
• Region restriction (error code 50125 or 80001): do NOT show the raw error code to the user. Instead, display a friendly message:

  ⚠️ Service is not available in your region. Please switch to a supported region and try again.

• Token amounts in UI units (

  1.5 ETH

  ), never base units (

  1500000000000000000

  )
• USD values with 2 decimal places
• Large amounts in shorthand (

  $1.2M

  )
• Sort by USD value descending

• --chains

  supports up to 50 chain IDs (comma-separated, names or numeric)

• --asset-type

  :

  0

  =all

  1

  =tokens only

  2

  =DeFi only (only for

  total-value

  )

• --exclude-risk

  only works on ETH(

  1

  )/BSC(

  56

  )/SOL(

  501

  )/BASE(

  8453

  )

• token-balances

  supports max 20 token entries
• The CLI resolves chain names automatically (e.g.,

  ethereum

  →

  1

  ,

  solana

  →

  501

  )
• The CLI handles authentication internally via environment variables — see Prerequisites step 4 for default values