Algo
Wire your agent or app to Binance Algo REST endpoints with correct HMAC, RSA, or Ed25519 signing and API credentials from env or files.
Overview
Algo is an agent skill for the Build phase that performs signed Binance Algo API requests using API key and secret credentials.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill algoWhat is this skill?
- Calls Binance Algo API with API key plus secret key authentication
- Supports credentials from environment variables or credential files
- Signature generation for HMAC, RSA, and Ed25519 key types
- Sets Openclaw metadata on the User Agent header (v1.1.0)
- Published from Binance skills hub with MIT license
- Skill metadata version 1.1.0 (2026-03-24 changelog)
- Supports HMAC, RSA, and Ed25519 signature generation for API requests
Adoption & trust: 1.2k installs on skills.sh; 881 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to call Binance Algo endpoints from an agent-driven codebase but signing, headers, and credential loading are easy to get wrong.
Who is it for?
Indie builders shipping a trading bot, internal tooling, or API backend that must talk to Binance Algo with proper auth.
Skip if: Builders who only need spot wallet or unrelated Binance products without Algo endpoints, or anyone who wants a no-code strategy platform with no API coding.
When should I use this skill?
You need to make authenticated Binance Algo API requests and want the agent to use the correct signing, headers, and credential sourcing.
What do I get? / Deliverables
Your agent issues correctly authenticated Binance Algo API requests with env- or file-based keys and supported signature algorithms so you can focus on strategy and app logic.
- Signed Binance Algo API request code or patches aligned with current skill conventions
- Credential and signature setup using env or file-based keys
Recommended Skills
Journey fit
Solo builders add this while implementing trading bots, automation, or backend services that call Binance’s Algo API—not during ideation or generic launch work. The skill is an external API integration (auth, signatures, requests), which maps directly to the build → integrations shelf.
How it compares
Use this skill for Binance Algo REST signing in-agent; it is not a hosted MCP server or a backtesting framework.
Common Questions / FAQ
Who is algo for?
Solo and indie developers using AI coding agents to integrate Binance Algo API calls into apps, CLIs, or agent workflows that require API key and secret authentication.
When should I use algo?
Use it during Build when you are implementing Binance Algo integrations—signed order or algo endpoints, credential setup from env or files, and header/signature fixes—before you ship or operate the bot in production.
Is algo safe to install?
It handles exchange API secrets and network access, so treat installs like any third-party skill: scope keys with withdrawals disabled where possible, never paste live secrets into prompts, and review the Security Audits panel on this Prism page before trusting it in production.
SKILL.md
READMESKILL.md - Algo
# Changelog ## 1.1.0 - 2026-03-24 - Environmental variables or files can now be used as input for the API key and secret key. - Fix signature generation for RSA and Ed25519 keys. - Add `Openclaw` metadata to the User Agent header ## 1.0.0 - 2026-03-19 - Initial release MIT License Copyright (c) 2026 Binance Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --- name: algo description: Binance Algo request using the Binance API. Authentication requires API key and secret key. metadata: version: 1.1.0 author: Binance openclaw: requires: bins: - curl - openssl - date homepage: https://github.com/binance/binance-skills-hub/tree/main/skills/binance/algo/SKILL.md license: MIT --- # Binance Algo Skill Algo 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 | |----------|-------------|----------|----------|----------------| | `/sapi/v1/algo/futures/order` (DELETE) | Cancel Algo Order(TRADE) | algoId | recvWindow | Yes | | `/sapi/v1/algo/futures/openOrders` (GET) | Query Current Algo Open Orders(USER_DATA) | None | recvWindow | Yes | | `/sapi/v1/algo/futures/historicalOrders` (GET) | Query Historical Algo Orders(USER_DATA) | None | symbol, side, startTime, endTime, page, pageSize, recvWindow | Yes | | `/sapi/v1/algo/futures/subOrders` (GET) | Query Sub Orders(USER_DATA) | algoId | page, pageSize, recvWindow | Yes | | `/sapi/v1/algo/futures/newOrderTwap` (POST) | Time-Weighted Average Price(Twap) New Order(TRADE) | symbol, side, quantity, duration | positionSide, clientAlgoId, reduceOnly, limitPrice, recvWindow | Yes | | `/sapi/v1/algo/futures/newOrderVp` (POST) | Volume Participation(VP) New Order (TRADE) | symbol, side, quantity, urgency | positionSide, clientAlgoId, reduceOnly, limitPrice, recvWindow | Yes | | `/sapi/v1/algo/spot/order` (DELETE) | Cancel Algo Order(TRADE) | algoId | recvWindow | Yes | | `/sapi/v1/algo/spot/openOrders` (GET) | Query Current Algo Open Orders(USER_DATA) | None | recvWindow | Yes | | `/sapi/v1/algo/spot/historicalOrders` (GET) | Query Historical Algo Orders(USER_DATA) | None | symbol, side, startTime, endTime, page, pageSize, recvWindow | Yes | | `/sapi/v1/algo/spot/subOrders` (GET) | Query Sub Orders(USER_DATA) | algoId | page, pageSize, recvWindow | Yes | | `/sapi/v1/algo/spot/newOrderTwap` (POST) | Time-Weighted Average Price(Twap) New Order(TRADE) | symbol, side, quantity, duration | clientAlgoId, limitPrice | Yes | --- ## Parameters ### Common Parameters * **algoId**: eg. 14511 (e.g., 1) * **recvWindow**: (e.g., 5000) * **symbol**: Trading symbol eg. BTCUSDT (e.g., BTCUSDT) * **side**: BUY or SELL (e.g., BUY) * **startTime**: in milliseconds eg.1641522717552 (e.g., 1623319461670) * **endTime**: in milliseconds eg.1641522526562 (e.g., 1641782889000) * **page**: Default is 1 (e.g., 1) * **pageSize**: MIN 1, MAX 10