Derivatives Trading Coin Futures

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 orders. (e.g., 1.0)

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:

• Mainnet: https://dapi.binance.com
• Testnet: https://testnet.binancefuture.com

Security

Share Credentials

Users can provide Binance API credentials by sending a file where the content is in the following format:

abc123...xyz
secret123...key

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.

Binance Accounts

main

• API Key: your_mainnet_api_key
• Secret: your_mainnet_secret
• Testnet: false

testnet-dev

• API Key: your_testnet_api_key
• Secret: your_testnet_secret
• Testnet: true

TOOLS.md Structure

## Binance Accounts

### main
- API Key: abc123...xyz
- Secret: secret123...key
- Testnet: false
- Description: Primary trading account

### testnet-dev
- API Key: test456...abc
- Secret: testsecret...xyz
- Testnet: true
- Description: Development/testing

### futures-keys
- API Key: futures789...def
- Secret: futuressecret...uvw
- Testnet: false
- Description: Futures trading account

Agent Behavior

1. Credentials requested: Mask secrets (show last 5 chars only)
2. Listing accounts: Show names and environment, never keys
3. Account selection: Ask if ambiguous, default to main
4. When doing a transaction in mainnet, confirm with user before by asking to write "CONFIRM" to proceed
5. New credentials: Prompt for name, environment, signing mode

Adding New Accounts

When user provides new credentials:

• Ask for account name
• Ask: Mainnet, Testnet
• Store in TOOLS.md with masked display confirmation

Signing Requests

For trading endpoints that require a signature:

1. Build query string with all parameters, including the timestamp (Unix ms).
2. Percent-encode the parameters using UTF-8 according to RFC 3986.
3. Sign query string with secretKey using HMAC SHA256, RSA, or Ed25519 (depending on the account configuration).
4. Append signature to query string.
5. Include X-MBX-APIKEY header.

Otherwise, do not perform steps 3–5.

New Client Order ID

For endpoints that include the newClientOrderId parameter, the value must always start with agent-. If the parameter is not provided, agent- followed by 18 random alphanumeric characters will be generated automatically. If a value is provided, it will be prefixed with agent-

Example: agent-1a2b3c4d5e6f7g8h9i

User Agent Header

Include User-Agent header with the following string: binance-derivatives-trading-coin-futures/1.0.0 (Skill)

See references/authentication.md for implementation details.