Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Derivatives-trading-options request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.
Cancel all Option orders on specific symbol (TRADE)
symbol
recvWindow
Yes
/eapi/v1/position (GET)
Option Position Information (USER_DATA)
None
symbol, recvWindow
Yes
/eapi/v1/openOrders (GET)
Query Current Open Option Orders (USER_DATA)
None
symbol, orderId, startTime, endTime, recvWindow
Yes
/eapi/v1/historyOrders (GET)
Query Option Order History (TRADE)
symbol
orderId, startTime, endTime, limit, recvWindow
Yes
/eapi/v1/commission (GET)
User Commission (USER_DATA)
None
recvWindow
Yes
/eapi/v1/exerciseRecord (GET)
User Exercise Record (USER_DATA)
None
symbol, startTime, endTime, limit, recvWindow
Yes
/eapi/v1/listenKey (DELETE)
Close User Data Stream (USER_STREAM)
None
None
No
/eapi/v1/listenKey (PUT)
Keepalive User Data Stream (USER_STREAM)
None
None
No
/eapi/v1/listenKey (POST)
Start User Data Stream (USER_STREAM)
None
None
No
Parameters
Common Parameters
currency: Asset type, only support USDT as of now
recordId: Return the recordId and subsequent data, the latest data is returned by default, e.g 100000 (e.g., 1)
startTime: Start Time, e.g 1593511200000 (e.g., 1623319461670)
endTime: End Time, e.g 1593512200000 (e.g., 1641782889000)
limit: Number of result sets returned Default:100 Max:1000 (e.g., 100)
recvWindow: (e.g., 5000)
blockOrderMatchingKey:
underlying: underlying, e.g BTCUSDT
liquidity: Taker or Maker
legs: Max 1 (only single leg supported), list of legs parameters in JSON; example: eapi/v1/block/order/create?orders=[{"symbol":"BTC-210115-35000-C", "price":"100","quantity":"0.0002","side":"BUY","type":"LIMIT"}]
blockOrderMatchingKey: If specified, returns the specific block trade associated with the blockOrderMatchingKey
countdownTime: Countdown time in milliseconds (ex. 1,000 for 1 second). 0 to disable the timer. Negative values (ex. -10000) are not accepted. Minimum acceptable value is 5,000
windowTimeInMilliseconds: MMP Interval in milliseconds; Range (0,5000]
frozenTimeInMilliseconds: MMP frozen time in milliseconds, if set to 0 manual reset is required
qtyLimit: quantity limit (e.g., 1.0)
deltaLimit: net delta limit (e.g., 1.0)
fromId: Trade id to fetch from. Default gets most recent trades, e.g 4611875134427365376 (e.g., 1)
orderIds: Order ID, e.g [4611875134427365377,4611875134427365378]
clientOrderIds: User-defined order ID, e.g ["my_id_1","my_id_2"]
orderId: Order ID, e.g 4611875134427365377 (e.g., 1)
clientOrderId: User-defined order ID, e.g 10000 (e.g., 1)
Users can provide Binance API credentials in different ways. The agent will try to retrieve automatically with the two first ways the credentials, but users can also explicitly tell the agent that they have set the credentials or stored them in a .env file, and the agent should re-read that file when they do. The agent can also make http requests with the two first methods without user confirmation.
Environment variables
Search for the following specific variables only (never dump the full environment):
Authorized environment variables
Mainnet: BINANCE_API_KEY and BINANCE_SECRET_KEY
Testnet: BINANCE_TESTNET_API_KEY and BINANCE_TESTNET_SECRET_KEY
Read and use in a single exec call so the raw key never enters the agent's context:
Environment variables must be set before OpenClaw starts. They are inherited at process startup and cannot be injected into a running instance. If you need to add or update credentials without restarting, use a secrets file (see option 2).
Secrets file (.env)
Check ~/.openclaw/secrets.env , ~/.env, or a .env file in the workspace. Read individual keys with grep, never source the full file:
# Try all credential locations in order
API_KEY=$(grep '^BINANCE_API_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-)
SECRET_KEY=$(grep '^BINANCE_SECRET_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-)
# Fallback: search .env in known directories (KEY=VALUE then raw line format)fordirin ~/.openclaw ~; do
[ -n "$API_KEY" ] && break
env_file="$dir/.env"
[ -f "$env_file" ] || continue# Read first two lines
line1=$(sed -n '1p'"$env_file")
line2=$(sed -n '2p'"$env_file")
# Check if lines contain '=' indicating KEY=VALUE formatif [[ "$line1" == *=* && "$line2" == *=* ]]; then
API_KEY=$(grep '^BINANCE_API_KEY='"$env_file" 2>/dev/null | cut -d= -f2-)
SECRET_KEY=$(grep '^BINANCE_SECRET_KEY='"$env_file" 2>/dev/null | cut -d= -f2-)
else# Treat lines as raw values
API_KEY="$line1"
SECRET_KEY="$line2"fidone
This file can be updated at any time without restarting OpenClaw, keys are read fresh on each invocation. Users can tell you the variables are now set or stored in a .env file, and you should re-read that file when they do.
Inline file
Sending a file where the content is in the following format:
abc123...xyz
secret123...key
Never run printenv, env, export, or set without a specific variable name
Never run grep on env files without anchoring to a specific key ('^VARNAME=')
Never source a secrets file into the shell environment (source .env or . .env)
Only read credentials explicitly needed for the current task
Never echo or log raw credentials in output or replies
Never commit TOOLS.md to version control if it contains real credentials — add it to .gitignore
Never Disclose API Key and Secret
Never disclose the location of the API key and secret file.
Never send the API key and secret to any website other than Mainnet and Testnet.
Never Display Full Secrets
When showing credentials to users:
API Key: Show first 5 + last 4 characters: su1Qc...8akf
Secret Key: Always mask, show only last 5: ***...aws1
Example response when asked for credentials:
Account: main
API Key: su1Qc...8akf
Secret: ***...aws1
Environment: Mainnet
Listing Accounts
When listing accounts, show names and environment only — never keys:
Binance Accounts:
main (Mainnet/Testnet)
testnet-dev (Testnet)
futures-keys (Mainnet)
Transactions in Mainnet
When performing transactions in mainnet, always confirm with the user before proceeding by asking them to write "CONFIRM" to proceed.
Credentials requested: Mask secrets (show last 5 chars only)
Listing accounts: Show names and environment, never keys
Account selection: Ask if ambiguous, default to main
When doing a transaction in mainnet, confirm with user before by asking to write "CONFIRM" to proceed
New credentials: Prompt for name, environment, signing mode
When a request requires signing, if the request isn't an order and the API keys aren't described as mainnet or testnet keys, try to make request to the different base urls and see if it works, without asking the user. If it works, store the keys with the corresponding environment.
Adding New Accounts
When user provides new credentials by Inline file or message:
Ask for account name
Ask: Mainnet, Testnet
Store in TOOLS.md with masked display confirmation
Signing Requests
For trading endpoints that require a signature:
Detect key type first, inspect the secret key format before signing.
Build query string with all parameters, including the timestamp (Unix ms).
Percent-encode the parameters using UTF-8 according to RFC 3986.
Sign query string with secretKey using HMAC SHA256, RSA, or Ed25519 (depending on the account configuration).
Append signature to query string.
Include X-MBX-APIKEY header.
Otherwise, do not perform steps 4–6.
User Agent Header
Include User-Agent header with the following string: binance-derivatives-trading-options/1.1.0 (Skill)
