/binance-agentic-wallet

Limit Order

Place, list, and cancel limit orders. A limit order executes automatically once the token hits the specified trigger price.

Security Pre-Check

Before executing limit-order buy or limit-order sell, complete the swap security pre-check in security.md §1. This includes auditing non-trusted target tokens and presenting the security summary to the user.

Fees

Limit orders are subject to Binance Web3 Wallet trading fees (charged when the order executes). For the current fee schedule, see: https://www.binance.com/en/support/faq/detail/87cbb1ca0df34a348eaecb73c26167d7

limit-order buy

Place a limit buy order — purchase a token using USDT, USDC, or BNB when it drops to the target price.

Syntax

baw limit-order buy --triggerPrice <triggerPrice> --fromTokenQty <fromTokenQty> --fromToken <fromToken> --toToken <toToken> --binanceChainId <binanceChainId> [--slippage <slippage>] [--mev <mev>] [--gasLevel <gasLevel>] --json

Parameters

Example

# Spend 100 USDT to buy a token when its price drops to $10
baw limit-order buy --triggerPrice 10 --fromTokenQty 100 --fromToken 0x55d398326f99059fF775485246999027B3197955 --toToken 0xcaca...1231 --binanceChainId 56 --json

# Spend 0.4 BNB to buy a token when its price drops to $5
baw limit-order buy --triggerPrice 5 --fromTokenQty 0.4 --fromToken 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE --toToken 0xcaca...1231 --binanceChainId 56 --json

Response

{ "success": true, "data": { "strategyId": "9876543210" } }

limit-order sell

Place a limit sell order — sell a token for USDT, USDC, or BNB when it reaches the target price.

Syntax

baw limit-order sell --triggerPrice <triggerPrice> --fromTokenQty <fromTokenQty> --fromToken <fromToken> --toToken <toToken> --binanceChainId <binanceChainId> [--slippage <slippage>] [--mev <mev>] [--gasLevel <gasLevel>] --json

Parameters

Example

# Sell 10.1 tokens for USDT when the price reaches $100
baw limit-order sell --triggerPrice 100 --fromTokenQty 10.1 --fromToken 0xcaca...1231 --toToken 0x55d398326f99059fF775485246999027B3197955 --binanceChainId 56 --json

# Sell 10.1 tokens for BNB when the price reaches $100
baw limit-order sell --triggerPrice 100 --fromTokenQty 10.1 --fromToken 0xcaca...1231 --toToken 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE --binanceChainId 56 --json

Response

{ "success": true, "data": { "strategyId": "9876543210" } }

limit-order list

List limit orders, optionally filtered by status, token, or time range.

Syntax

baw limit-order list [--strategyId <strategyId>] [--status <status>] [--fromToken <fromToken>] [--toToken <toToken>] [--startTime <startTime>] [--endTime <endTime>] [--page <page>] [--pageSize <pageSize>] [--binanceChainId <binanceChainId>] --json

Parameters

Example

# List all limit orders
baw limit-order list --json

# Look up a specific limit order
baw limit-order list --strategyId 9876543210 --json

# List active (working) limit orders
baw limit-order list --status WORKING --json

Response

{
  "success": true,
  "data": {
    "total": 1,
    "page": 1,
    "pageSize": 20,
    "list": [
      {
        "orderType": "limit",
        "strategyId": "9876543210",
        "chain": "56",
        "side": "SELL",
        "fromToken": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
        "fromTokenName": "BNB",
        "fromTokenQty": "1.0",
        "toToken": "0x55d398326f99059fF775485246999027B3197955",
        "toTokenName": "USDT",
        "triggerPrice": "600",
        "status": "WORKING",
        "slippage": "0.1",
        "txHash": null,
        "bookTime": "2026-04-01T19:14:52+08:00",
        "updatedTime": "2026-04-01T19:14:52+08:00"
      }
    ]
  }
}

Limit Order Status

⚠️ Mandatory: a strategyId is NOT a fill

A success: true response with a strategyId from limit-order buy / limit-order sell means the order has been placed. It does not mean anything was bought or sold. Reporting a placement as a completed trade is a real failure mode.

1. Report a placement as a placement. Say the order has been placed and state the trigger price. Never say the user bought or sold anything at this point.
2. WORKING is the expected resting state, not "still processing". A limit order waits for its trigger price and can sit in WORKING for days. Tell the user it is resting and how to check it later (limit-order list --strategyId <id> --json) — do not poll a WORKING order to a terminal state, and do not imply it is about to execute.
3. Once the status reaches TRIGGERED or PENDING, the order is actually executing. Only then does polling to a terminal state make sense.
4. Report each terminal status for what it is:
   • FINISHED → filled; include txHash and the actual amount.
   • FAILED → on-chain execution failed; say so plainly.
   • EXPIRED → the trigger price was never reached and the order is dead. Tell the user — do not leave it looking like it is still waiting.
   • CANCELED → canceled. Same: state it explicitly.

EXPIRED and CANCELED are the ones most easily misreported as "still pending". Neither will ever execute.

limit-order cancel

Cancel a limit order by its strategy ID. Orders that have already been executed cannot be canceled.

Syntax

baw limit-order cancel --strategyId <strategyId> --json

Parameters

Example

baw limit-order cancel --strategyId 9876543210 --json

Response

{ "success": true, "data": { "strategyId": "9876543210", "status": "CANCELED" } }