derivatives-trading-coin-futures

binance/binance-skills-hub · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/binance/binance-skills-hub --skill derivatives-trading-coin-futures
0 commentsdiscussion
summary

Derivatives-trading-coin-futures request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.

skill.md

Binance Derivatives-trading-coin-futures Skill

Derivatives-trading-coin-futures request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.

Quick Reference

Endpoint Description Required Optional Authentication
/dapi/v1/account (GET) Account Information (USER_DATA) None recvWindow Yes
/dapi/v1/balance (GET) Futures Account Balance (USER_DATA) None recvWindow Yes
/dapi/v1/positionSide/dual (GET) Get Current Position Mode(USER_DATA) None recvWindow Yes
/dapi/v1/positionSide/dual (POST) Change Position Mode(TRADE) dualSidePosition recvWindow Yes
/dapi/v1/order/asyn (GET) Get Download Id For Futures Order History (USER_DATA) startTime, endTime recvWindow Yes
/dapi/v1/trade/asyn (GET) Get Download Id For Futures Trade History (USER_DATA) startTime, endTime recvWindow Yes
/dapi/v1/income/asyn (GET) Get Download Id For Futures Transaction History(USER_DATA) startTime, endTime recvWindow Yes
/dapi/v1/order/asyn/id (GET) Get Futures Order History Download Link by Id (USER_DATA) downloadId recvWindow Yes
/dapi/v1/trade/asyn/id (GET) Get Futures Trade Download Link by Id(USER_DATA) downloadId recvWindow Yes
/dapi/v1/income/asyn/id (GET) Get Futures Transaction History Download Link by Id (USER_DATA) downloadId recvWindow Yes
/dapi/v1/income (GET) Get Income History(USER_DATA) None symbol, incomeType, startTime, endTime, page, limit, recvWindow Yes
/dapi/v1/leverageBracket (GET) Notional Bracket for Pair(USER_DATA) None pair, recvWindow Yes
/dapi/v2/leverageBracket (GET) Notional Bracket for Symbol(USER_DATA) None symbol, recvWindow Yes
/dapi/v1/commissionRate (GET) User Commission Rate (USER_DATA) symbol recvWindow Yes
/dapi/v1/ticker/24hr (GET) 24hr Ticker Price Change Statistics None symbol, pair No
/futures/data/basis (GET) Basis pair, contractType, period limit, startTime, endTime No
/dapi/v1/time (GET) Check Server time None None No
/dapi/v1/aggTrades (GET) Compressed/Aggregate Trades List symbol fromId, startTime, endTime, limit No
/dapi/v1/continuousKlines (GET) Continuous Contract Kline/Candlestick Data pair, contractType, interval startTime, endTime, limit No
/dapi/v1/exchangeInfo (GET) Exchange Information None None No
/dapi/v1/fundingInfo (GET) Get Funding Rate Info None None No
/dapi/v1/fundingRate (GET) Get Funding Rate History of Perpetual Futures symbol startTime, endTime, limit No
/dapi/v1/constituents (GET) Query Index Price Constituents symbol None No
/dapi/v1/indexPriceKlines (GET) Index Price Kline/Candlestick Data pair, interval startTime, endTime, limit No
/dapi/v1/premiumIndex (GET) Index Price and Mark Price None symbol, pair No
/dapi/v1/klines (GET) Kline/Candlestick Data symbol, interval startTime, endTime, limit No
/futures/data/globalLongShortAccountRatio (GET) Long/Short Ratio pair, period limit, startTime, endTime No
/dapi/v1/markPriceKlines (GET) Mark Price Kline/Candlestick Data symbol, interval startTime, endTime, limit No
/dapi/v1/historicalTrades (GET) Old Trades Lookup(MARKET_DATA) symbol limit, fromId No
/futures/data/openInterestHist (GET) Open Interest Statistics pair, contractType, period limit, startTime, endTime No
/dapi/v1/openInterest (GET) Open Interest symbol None No
/dapi/v1/depth (GET) Order Book symbol limit No
/dapi/v1/premiumIndexKlines (GET) Premium index Kline Data symbol, interval startTime, endTime, limit No
/dapi/v1/trades (GET) Recent Trades List symbol limit No
/dapi/v1/ticker/bookTicker (GET) Symbol Order Book Ticker None symbol, pair No
/dapi/v1/ticker/price (GET) Symbol Price Ticker None symbol, pair No
/futures/data/takerBuySellVol (GET) Taker Buy/Sell Volume pair, contractType, period limit, startTime, endTime No
/dapi/v1/ping (GET) Test Connectivity None None No
/futures/data/topLongShortAccountRatio (GET) Top Trader Long/Short Ratio (Accounts) symbol, period limit, startTime, endTime No
/futures/data/topLongShortPositionRatio (GET) Top Trader Long/Short Ratio (Positions) pair, period limit, startTime, endTime No
/dapi/v1/pmAccountInfo (GET) Classic Portfolio Margin Account Information (USER_DATA) asset recvWindow Yes
/dapi/v1/userTrades (GET) Account Trade List (USER_DATA) None symbol, pair, orderId, startTime, endTime, fromId, limit, recvWindow Yes
/dapi/v1/allOrders (GET) All Orders (USER_DATA) None symbol, pair, orderId, startTime, endTime, limit, recvWindow Yes
/dapi/v1/countdownCancelAll (POST) Auto-Cancel All Open Orders (TRADE) symbol, countdownTime recvWindow Yes
/dapi/v1/allOpenOrders (DELETE) Cancel All Open Orders(TRADE) symbol recvWindow Yes
/dapi/v1/batchOrders (DELETE) Cancel Multiple Orders(TRADE) symbol orderIdList, origClientOrderIdList, recvWindow Yes
/dapi/v1/batchOrders (PUT) Modify Multiple Orders(TRADE) batchOrders recvWindow Yes
/dapi/v1/batchOrders (POST) Place Multiple Orders(TRADE) batchOrders recvWindow Yes
/dapi/v1/order (DELETE) Cancel Order (TRADE) symbol orderId, origClientOrderId, recvWindow Yes
/dapi/v1/order (PUT) Modify Order (TRADE) symbol, side orderId, origClientOrderId, quantity, price, priceMatch, recvWindow Yes
/dapi/v1/order (POST) New Order (TRADE) symbol, side, type positionSide, timeInForce, quantity, reduceOnly, price, newClientOrderId, stopPrice, closePosition, activationPrice, callbackRate, workingType, priceProtect, newOrderRespType, priceMatch, selfTradePreventionMode, recvWindow Yes
/dapi/v1/order (GET) Query Order (USER_DATA) symbol orderId, origClientOrderId, recvWindow Yes
/dapi/v1/leverage (POST) Change Initial Leverage (TRADE) symbol, leverage recvWindow Yes
/dapi/v1/marginType (POST) Change Margin Type (TRADE) symbol, marginType recvWindow Yes
/dapi/v1/openOrders (GET) Current All Open Orders (USER_DATA) None symbol, pair, recvWindow Yes
/dapi/v1/orderAmendment (GET) Get Order Modify History (USER_DATA) symbol orderId, origClientOrderId, startTime, endTime, limit, recvWindow Yes
/dapi/v1/positionMargin/history (GET) Get Position Margin Change History(TRADE) symbol type, startTime, endTime, limit, recvWindow Yes
/dapi/v1/positionMargin (POST) Modify Isolated Position Margin(TRADE) symbol, amount, type positionSide, recvWindow Yes
/dapi/v1/adlQuantile (GET) Position ADL Quantile Estimation(USER_DATA) None symbol, recvWindow Yes
/dapi/v1/positionRisk (GET) Position Information(USER_DATA) None marginAsset, pair, recvWindow Yes
/dapi/v1/openOrder (GET) Query Current Open Order(USER_DATA) symbol orderId, origClientOrderId, recvWindow Yes
/dapi/v1/forceOrders (GET) User's Force Orders(USER_DATA) None symbol, autoCloseType, startTime, endTime, limit, recvWindow Yes
/dapi/v1/listenKey (DELETE) Close User Data Stream(USER_STREAM) None None No
/dapi/v1/listenKey (PUT) Keepalive User Data Stream (USER_STREAM) None None No
/dapi/v1/listenKey (POST) Start User Data Stream (USER_STREAM) None None No

Parameters

Common Parameters

  • recvWindow: (e.g., 5000)
  • startTime: Timestamp in ms (e.g., 1623319461670)
  • endTime: Timestamp in ms (e.g., 1641782889000)
  • downloadId: get by download id api (e.g., 1)
  • symbol:
  • incomeType: "TRANSFER","WELCOME_BONUS", "FUNDING_FEE", "REALIZED_PNL", "COMMISSION", "INSURANCE_CLEAR", and "DELIVERED_SETTELMENT"
  • startTime: (e.g., 1623319461670)
  • endTime: (e.g., 1641782889000)
  • page:
  • limit: Default 100; max 1000 (e.g., 100)
  • pair:
  • symbol:
  • pair: BTCUSD
  • fromId: ID to get aggregate trades from INCLUSIVE. (e.g., 1)
  • asset:
  • orderId: (e.g., 1)
  • orderId: (e.g., 1)
  • countdownTime: countdown time, 1000 for 1 second. 0 to cancel the timer
  • orderIdList: max length 10 e.g. [1234567,2345678]
  • origClientOrderIdList: max length 10 e.g. ["my_id_1","my_id_2"], encode the double quotes. No space after comma.
  • origClientOrderId: (e.g., 1)
  • leverage: target initial leverage: int from 1 to 125
  • dualSidePosition: "true": Hedge Mode; "false": One-way Mode
  • type: 1: Add position margin,2: Reduce position margin
  • amount: (e.g., 1.0)
  • batchOrders: order list. Max 5 orders
  • quantity: quantity measured by contract number, Cannot be sent with closePosition=true (e.g., 1.0)
  • price: (e.g., 1.0)
  • reduceOnly: "true" or "false". default "false". Cannot be sent in Hedge Mode; cannot be sent with closePosition=true(Close-All)
  • newClientOrderId: A unique id among open orders. Automatically generated if not sent. Can only be string following the rule: ^[\.A-Z\:/a-z0-9_-]{1,36}$ (e.g., 1)
  • stopPrice: Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders. (e.g., 1.0)
  • closePosition: true, false;Close-All,used with STOP_MARKET or TAKE_PROFIT_MARKET.
  • activationPrice: Used with TRAILING_STOP_MARKET orders, default as the latest price(supporting different workingType) (e.g., 1.0)
  • callbackRate: Used with TRAILING_STOP_MARKET orders, min 0.1, max 10 where 1 for 1% (e.g., 1.0)
  • priceProtect: "TRUE" or "FALSE", default "FALSE". Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.
  • batchOrders: order list. Max 5 orders
  • marginAsset:

Enums

  • contractType: PERPETUAL | CURRENT_QUARTER | NEXT_QUARTER | CURRENT_QUARTER_DELIVERING | NEXT_QUARTER_DELIVERING | PERPETUAL_DELIVERING
  • period: 5m | 15m | 30m | 1h | 2h | 4h | 6h | 12h | 1d
  • interval: 1m | 3m | 5m | 15m | 30m | 1h | 2h | 4h | 6h | 8h | 12h | 1d | 3d | 1w | 1M
  • marginType: ISOLATED | CROSSED
  • positionSide: BOTH | LONG | SHORT
  • type: LIMIT | MARKET | STOP | STOP_MARKET | TAKE_PROFIT | TAKE_PROFIT_MARKET | TRAILING_STOP_MARKET
  • side: BUY | SELL
  • priceMatch: NONE | OPPONENT | OPPONENT_5 | OPPONENT_10 | OPPONENT_20 | QUEUE | QUEUE_5 | QUEUE_10 | QUEUE_20
  • timeInForce: GTC | IOC | FOK | GTX
  • workingType: MARK_PRICE | CONTRACT_PRICE
  • newOrderRespType: ACK | RESULT
  • selfTradePreventionMode: NONE | EXPIRE_TAKER | EXPIRE_BOTH | EXPIRE_MAKER
  • autoCloseType: LIQUIDATION | ADL

Authentication

For endpoints that require authentication, you will need to provide Binance API credentials. Required credentials:

  • apiKey: Your Binance API key (for header)
  • secretKey: Your Binance API secret (for signing)

Base URLs:

Security

Share Credentials

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.

  1. 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:

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).

  1. 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)
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" == *=* ]]
how to use derivatives-trading-coin-futures

How to use derivatives-trading-coin-futures on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add derivatives-trading-coin-futures
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/binance/binance-skills-hub --skill derivatives-trading-coin-futures

The skills CLI fetches derivatives-trading-coin-futures from GitHub repository binance/binance-skills-hub and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/derivatives-trading-coin-futures

Reload or restart Cursor to activate derivatives-trading-coin-futures. Access the skill through slash commands (e.g., /derivatives-trading-coin-futures) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.532 reviews
  • Noor Ramirez· Dec 12, 2024

    derivatives-trading-coin-futures is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Jin Jackson· Nov 7, 2024

    derivatives-trading-coin-futures reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Diego Patel· Oct 26, 2024

    Registry listing for derivatives-trading-coin-futures matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Jin Wang· Sep 17, 2024

    Useful defaults in derivatives-trading-coin-futures — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Anaya Abebe· Sep 5, 2024

    We added derivatives-trading-coin-futures from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yash Thakker· Sep 1, 2024

    We added derivatives-trading-coin-futures from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Olivia Jackson· Aug 24, 2024

    derivatives-trading-coin-futures fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Aug 20, 2024

    derivatives-trading-coin-futures fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mei Ghosh· Aug 8, 2024

    I recommend derivatives-trading-coin-futures for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Olivia Li· Jul 27, 2024

    Solid pick for teams standardizing on skills: derivatives-trading-coin-futures is focused, and the summary matches what you get after install.

showing 1-10 of 32

1 / 4