Binance API

What This Skill Does

The Binance API skill for OpenClaw empowers AI agents to securely interact with the Binance Spot exchange ecosystem. It acts as a specialized wrapper for REST, WebSocket, and SDK workflows, ensuring that all operations—from market data analysis to trade execution—are performed with rigorous safety protocols. The skill handles the complexities of HMAC-SHA256 request signing, server time synchronization, and parameter serialization. It is designed to be self-documenting and stateful, utilizing a local ~/binance/ directory to track symbol filters, trade history, and previous incident resolutions. By enforcing a testnet-first policy, it allows developers and automated agents to validate strategies and order payloads without risking real capital, ensuring that every request meets strict exchange requirements before hitting production servers.

Installation

To integrate this skill, use the command: clawhub install openclaw/skills/skills/ivangdavila/binance. Ensure your system has curl, openssl, and jq installed. You must configure your BINANCE_API_KEY and BINANCE_API_SECRET in your local environment variables—never embed these in code. Initialize your environment by reading the setup.md file located within the installation directory.

Use Cases

• Automated Trading: Execute complex buy/sell orders that automatically account for PRICE_FILTER, LOT_SIZE, and MIN_NOTIONAL constraints.
• Market Analysis: Stream real-time price updates via WebSockets for low-latency observation.
• Portfolio Monitoring: Fetch balance snapshots and track order fills through event-driven reconciliation.
• Risk Mitigation: Use the testnet environment to debug new trading logic and payload formatting without exposing funds to actual market volatility.

Example Prompts

1. "Check the current exchangeInfo for BTCUSDT and tell me if a 0.001 BTC order meets the LOT_SIZE requirements."
2. "Run a test order in the Binance Testnet for 100 USDT worth of BNB to verify my current API signing logic."
3. "Sync the server time and pull my last 5 order execution reports from the account history."

Tips & Limitations

• Always Start in Testnet: The agent is programmed to prioritize testnet environments. Only switch to production after explicit user authorization.
• Respect Rate Limits: Always monitor HTTP headers for rate limit consumption. The agent will automatically back off when 429 or 418 status codes are detected.
• Safety First: Treat all POST requests as provisional. Use the reconciliation workflow to confirm state against the executionReport stream.
• Environment Sync: Keep your ~/binance/ directory updated. If you experience failures, check the incidents.md file to see if similar errors have been recorded and resolved previously.