Alpha
Authenticate and call Binance Alpha API endpoints from your agent with correct signing for API key, secret, RSA, or Ed25519 credentials.
Overview
alpha is an agent skill for the Build phase that performs authenticated Binance Alpha API requests with API key, secret, and supported signature schemes.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill alphaWhat is this skill?
- Binance Alpha requests with API key and secret (or env/file-backed credentials)
- Signature generation fixes for RSA and Ed25519 keys in v1.1.0
- OpenClaw metadata included in User-Agent header for agent attribution
- MIT-licensed Binance hub skill with changelog-tracked API behavior
- Skill metadata version 1.1.0 with RSA/Ed25519 signature fixes noted in changelog
Adoption & trust: 2k installs on skills.sh; 881 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Binance Alpha calls from an agent but keep getting auth or signature errors across HMAC, RSA, and Ed25519 key types.
Who is it for?
Indie devs building crypto trading agents, CLI automations, or backend services that already have Binance API credentials and need reliable request signing.
Skip if: Non-crypto products, paper trading without real keys, or users who need tax, compliance, or investment advice rather than API integration steps.
When should I use this skill?
User needs Binance Alpha API requests with API key and secret authentication.
What do I get? / Deliverables
Your agent follows the hub skill’s signing and credential patterns so Alpha API requests authenticate consistently using env, file, or inline keys.
- Authenticated Binance Alpha HTTP requests
- Correct request signatures per key type
Recommended Skills
Journey fit
Exchange API wiring is build-time integration work once you are implementing trading, portfolio, or market-data features in your product. Integrations is the shelf for third-party API clients and auth patterns—not launch SEO or ship security review checklists.
How it compares
Skill-packaged Binance Alpha client guidance, not a hosted MCP server or exchange UI.
Common Questions / FAQ
Who is alpha for?
Developers and agent builders integrating Binance Alpha who want documented auth and signing behavior in a reusable SKILL.md instead of one-off scripts.
When should I use alpha?
During Build integrations while wiring market data, orders, or account endpoints into your SaaS, CLI, or agent backend.
Is alpha safe to install?
It requires API secrets and network access—review the Security Audits panel on this page, never commit keys, and scope Binance API permissions to least privilege.
SKILL.md
READMESKILL.md - Alpha
# 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-10 - 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: alpha description: Binance Alpha 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/alpha/SKILL.md license: MIT --- # Binance Alpha Skill Alpha 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 | |----------|-------------|----------|----------|----------------| | `/bapi/defi/v1/public/alpha-trade/ticker` (GET) | Ticker (24hr Price Statistics) | symbol | None | No | | `/bapi/defi/v1/public/alpha-trade/agg-trades` (GET) | Aggregated Trades | symbol | fromId, startTime, endTime, limit | No | | `/bapi/defi/v1/public/alpha-trade/get-exchange-info` (GET) | Get Exchange Info | None | None | No | | `/bapi/defi/v1/public/alpha-trade/klines` (GET) | Klines (Candlestick Data) | symbol, interval | limit, startTime, endTime | No | | `/bapi/defi/v1/public/wallet-direct/buw/wallet/cex/alpha/all/token/list` (GET) | Token List | None | None | No | --- ## Parameters ### Common Parameters * **symbol**: e.g., "ALPHA_175USDT" – use token ID from Token List * **fromId**: starting trade ID to fetch from (e.g., 1) * **startTime**: start timestamp (milliseconds) (e.g., 1623319461670) * **endTime**: end timestamp (milliseconds) (e.g., 1641782889000) * **limit**: number of results to return (default 500, max 1000) (e.g., 500) * **interval**: e.g., "1h" – supported intervals: 1s, 15s, 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M ## 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://www.binance.com ## 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** - Mainn