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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionderivatives-trading-optionsExecute the skills CLI command in your project's root directory to begin installation:
Fetches derivatives-trading-options from binance/binance-skills-hub and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate derivatives-trading-options. Access via /derivatives-trading-options in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
676
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
676
stars
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.
| Endpoint | Description | Required | Optional | Authentication |
|---|---|---|---|---|
/eapi/v1/bill (GET) |
Account Funding Flow (USER_DATA) | currency | recordId, startTime, endTime, limit, recvWindow | Yes |
/eapi/v1/marginAccount (GET) |
Option Margin Account Information (USER_DATA) | None | recvWindow | Yes |
/eapi/v1/block/order/execute (POST) |
Accept Block Trade Order (TRADE) | blockOrderMatchingKey | recvWindow | Yes |
/eapi/v1/block/order/execute (GET) |
Query Block Trade Details (USER_DATA) | blockOrderMatchingKey | recvWindow | Yes |
/eapi/v1/block/user-trades (GET) |
Account Block Trade List (USER_DATA) | None | endTime, startTime, underlying, recvWindow | Yes |
/eapi/v1/block/order/create (DELETE) |
Cancel Block Trade Order (TRADE) | blockOrderMatchingKey | recvWindow | Yes |
/eapi/v1/block/order/create (PUT) |
Extend Block Trade Order (TRADE) | blockOrderMatchingKey | recvWindow | Yes |
/eapi/v1/block/order/create (POST) |
New Block Trade Order (TRADE) | liquidity, legs | recvWindow | Yes |
/eapi/v1/block/order/orders (GET) |
Query Block Trade Order (TRADE) | None | blockOrderMatchingKey, endTime, startTime, underlying, recvWindow | Yes |
/eapi/v1/ticker (GET) |
24hr Ticker Price Change Statistics | None | symbol | No |
/eapi/v1/time (GET) |
Check Server Time | None | None | No |
/eapi/v1/exchangeInfo (GET) |
Exchange Information | None | None | No |
/eapi/v1/exerciseHistory (GET) |
Historical Exercise Records | None | underlying, startTime, endTime, limit | No |
/eapi/v1/klines (GET) |
Kline/Candlestick Data | symbol, interval | startTime, endTime, limit | No |
/eapi/v1/openInterest (GET) |
Open Interest | underlyingAsset, expiration | None | No |
/eapi/v1/mark (GET) |
Option Mark Price | None | symbol | No |
/eapi/v1/depth (GET) |
Order Book | symbol | limit | No |
/eapi/v1/blockTrades (GET) |
Recent Block Trades List | None | symbol, limit | No |
/eapi/v1/trades (GET) |
Recent Trades List | symbol | limit | No |
/eapi/v1/index (GET) |
Index Price | underlying | None | No |
/eapi/v1/ping (GET) |
Test Connectivity | None | None | No |
/eapi/v1/countdownCancelAllHeartBeat (POST) |
Auto-Cancel All Open Orders (Kill-Switch) Heartbeat (TRADE) | underlyings | recvWindow | Yes |
/eapi/v1/countdownCancelAll (GET) |
Get Auto-Cancel All Open Orders (Kill-Switch) Config (TRADE) | None | underlying, recvWindow | Yes |
/eapi/v1/countdownCancelAll (POST) |
Set Auto-Cancel All Open Orders (Kill-Switch) Config (TRADE) | underlying, countdownTime | recvWindow | Yes |
/eapi/v1/mmp (GET) |
Get Market Maker Protection Config (TRADE) | None | underlying, recvWindow | Yes |
/eapi/v1/mmpReset (POST) |
Reset Market Maker Protection Config (TRADE) | None | underlying, recvWindow | Yes |
/eapi/v1/mmpSet (POST) |
Set Market Maker Protection Config (TRADE) | None | underlying, windowTimeInMilliseconds, frozenTimeInMilliseconds, qtyLimit, deltaLimit, recvWindow | Yes |
/eapi/v1/userTrades (GET) |
Account Trade List (USER_DATA) | None | symbol, fromId, startTime, endTime, limit, recvWindow | Yes |
/eapi/v1/allOpenOrdersByUnderlying (DELETE) |
Cancel All Option Orders By Underlying (TRADE) | underlying | recvWindow | Yes |
/eapi/v1/batchOrders (DELETE) |
Cancel Multiple Option Orders (TRADE) | symbol | orderIds, clientOrderIds, recvWindow | Yes |
/eapi/v1/batchOrders (POST) |
Place Multiple Orders(TRADE) | orders | recvWindow | Yes |
/eapi/v1/order (DELETE) |
Cancel Option Order (TRADE) | symbol | orderId, clientOrderId, recvWindow | Yes |
/eapi/v1/order (POST) |
New Order (TRADE) | symbol, side, type, quantity | price, timeInForce, reduceOnly, postOnly, newOrderRespType, clientOrderId, isMmp, recvWindow | Yes |
/eapi/v1/order (GET) |
Query Single Order (TRADE) | symbol | orderId, clientOrderId, recvWindow | Yes |
/eapi/v1/allOpenOrders (DELETE) |
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 |
For endpoints that require authentication, you will need to provide Binance API credentials. Required credentials:
Base URLs:
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.
Search for the following specific variables only (never dump the full environment):
Authorized environment variables
BINANCE_API_KEY and BINANCE_SECRET_KEYBINANCE_TESTNET_API_KEY and BINANCE_TESTNET_SECRET_KEYRead and use in a single exec call so the raw key never enters the agent's context:
KEY="$BINANCE_API_KEY"
SECRET="$BINANCE_SECRET_KEY"
response=$(curl -s -X GET "$URL" \
-H "X-MBX-APIKEY: $KEY" \
--data-urlencode "param1=value1")
echo "$response"
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).
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)
for dir in ~/.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 format
if [[ "$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"
fi
done
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.
Sending a file where the content is in the following format:
abc123...xyz
secret123...key
printenv, env, export, or set without a specific variable namegrep on env files without anchoring to a specific key ('^VARNAME=')source .env or . .env)TOOLS.md to version control if it contains real credentials — add it to .gitignoreNever 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.
When showing credentials to users:
su1Qc...8akf***...aws1Example response when asked for credentials: Account: main API Key: su1Qc...8akf Secret: ***...aws1 Environment: Mainnet
When listing accounts, show names and environment only — never keys: Binance Accounts:
When performing transactions in mainnet, always confirm with the user before proceeding by asking them to write "CONFIRM" to proceed.
## Binance Accounts
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
huynguyen03dev/xauusd-trading
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: derivatives-trading-options is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: derivatives-trading-options is focused, and the summary matches what you get after install.
Registry listing for derivatives-trading-options matched our evaluation — installs cleanly and behaves as described in the markdown.
We added derivatives-trading-options from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
derivatives-trading-options fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
derivatives-trading-options is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for derivatives-trading-options matched our evaluation — installs cleanly and behaves as described in the markdown.
derivatives-trading-options reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend derivatives-trading-options for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for derivatives-trading-options matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 50