derivatives-trading-options

Name: derivatives-trading-options
Availability: InStock
Author: tradecatlabs

Execute authenticated Binance Derivatives options trading requests via signed API endpoints.

957|244|Updated Dec 30, 2025

Search Tags:#binance #options api #request signing #authenticated requests #json responses #mainnet testnet

Ready to run

npx skills add https://github.com/tradecatlabs/tradecat-public --skill derivatives-trading-options-tradecatlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: derivatives-trading-options
Source: https://github.com/tradecatlabs/tradecat-public/tree/main/resources/agent_market_context/binance/upstream/binance-skills-hub-main/skills/binance/derivatives-trading-options
Command: npx skills add https://github.com/tradecatlabs/tradecat-public --skill derivatives-trading-options-tradecatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of retrieving and executing Binance Derivatives options actions reliably through the official authenticated API, instead of manually constructing requests and handling signing details.

Core Features & Use Cases

Authenticated option endpoints: Fetch option market data (e.g., tickers, klines, mark price, open interest) and perform authenticated user actions where required.
Signed request support: Handles API key/secret authentication and signing for HMAC SHA256, RSA, or Ed25519, with mainnet/testnet base URLs.
Operational safety for integration: Provides deterministic request semantics and JSON responses suitable for agent tool use rather than interactive trading UI.
Use Case: When an agent needs to validate option context (e.g., open interest, index price, mark price) and then query or execute option-related authenticated actions using request parameters and signatures.

Quick Start

Ask your agent to call derivatives-trading-options to GET /eapi/v1/time on testnet and return the server time in JSON.

Frequently Asked Questions about derivatives-trading-options

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I authenticate Binance options API requests for trading?▼

Binance options API requests require API credentials and request signing using HMAC SHA256, RSA, or Ed25519. Authenticated endpoints must include the X-MBX-APIKEY header, User-Agent header, and RFC 3986 percent-encoding for parameters.

Can I use Binance testnet for options trading API integration?▼

Yes, Binance testnet is supported for options trading API integration. The Skill provides mainnet and testnet base URLs, allowing you to validate option context like open interest and mark price before executing authenticated actions on mainnet.

What Binance options market data can I retrieve through the API?▼

You can retrieve Binance options market data including tickers, klines, mark price, open interest, and index price. These public endpoints provide option market context necessary for validating trades and analyzing current market conditions.

How do I create and cancel option orders on Binance programmatically?▼

To create or cancel Binance option orders programmatically, make authenticated POST or DELETE requests to the appropriate user-data endpoints. The Skill handles order creation, cancellation, and account queries using signed API requests.

Do I need API credentials for public Binance options endpoints?▼

No, API credentials are not required for public Binance options endpoints retrieving market data like tickers or klines. Credentials and request signing are only required for authenticated user-data endpoints performing actions like order creation.