npx skills add https://github.com/binance/binance-skills-hub --skill fiat使用经过身份验证的 API 端点进行 Binance 法币请求。某些端点需要 API 密钥和密钥。以 JSON 格式返回结果。
| 端点 | 描述 | 必需参数 | 可选参数 | 身份验证 |
|---|---|---|---|---|
/sapi/v1/fiat/deposit (POST) | 存款(TRADE) | 无 | recvWindow | 是 |
/sapi/v2/fiat/withdraw (POST) | 法币提现(WITHDRAW) | 无 | recvWindow | 是 |
/sapi/v1/fiat/orders (GET) | 获取法币存款/提现历史 (USER_DATA) |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者，精准高效
| transactionType |
| beginTime, endTime, page, rows, recvWindow |
| 是 |
/sapi/v1/fiat/payments (GET) | 获取法币支付历史 (USER_DATA) | transactionType | beginTime, endTime, page, rows, recvWindow | 是 |
/sapi/v1/fiat/get-order-detail (GET) | 获取订单详情(USER_DATA) | orderNo | recvWindow | 是 |
对于需要身份验证的端点，您需要提供 Binance API 凭据。所需凭据：
基础 URL：
用户可以通过发送文件来提供 Binance API 凭据，文件内容格式如下：
abc123...xyz
secret123...key
切勿泄露 API 密钥和密钥文件的位置。
切勿将 API 密钥和密钥发送到主网和测试网以外的任何网站。
向用户显示凭据时：
su1Qc...8akf***...aws1当被要求提供凭据时的示例响应：账户: main API 密钥: su1Qc...8akf 密钥: ***...aws1
列出账户时，仅显示名称和环境 — 切勿显示密钥：Binance 账户：
在主网执行交易时，务必在继续之前通过要求用户输入 "CONFIRM" 来与用户确认。
## Binance 账户
### main
- API 密钥: abc123...xyz
- 密钥: secret123...key
- 描述: 主要交易账户
### futures-keys
- API 密钥: futures789...def
- 密钥: futuressecret...uvw
- 描述: 期货交易账户
当用户提供新凭据时：
TOOLS.md 中，并显示掩码后的确认信息对于需要签名的交易端点：
X-MBX-APIKEY 请求头。否则，不执行步骤 3–5。
包含 User-Agent 请求头，其字符串如下：binance-fiat/1.0.0 (Skill)
有关实现细节，请参见 references/authentication.md。
每周安装量
210
代码仓库
GitHub 星标数
516
首次出现
4 天前
安全审计
安装于
codex199
opencode199
gemini-cli197
kimi-cli197
cursor197
github-copilot197
Fiat request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.
| Endpoint | Description | Required | Optional | Authentication |
|---|---|---|---|---|
/sapi/v1/fiat/deposit (POST) | Deposit(TRADE) | None | recvWindow | Yes |
/sapi/v2/fiat/withdraw (POST) | Fiat Withdraw(WITHDRAW) | None | recvWindow | Yes |
/sapi/v1/fiat/orders (GET) | Get Fiat Deposit/Withdraw History (USER_DATA) | transactionType | beginTime, endTime, page, rows, recvWindow | Yes |
/sapi/v1/fiat/payments (GET) | Get Fiat Payments History (USER_DATA) | transactionType | beginTime, endTime, page, rows, recvWindow | Yes |
/sapi/v1/fiat/get-order-detail (GET) | Get Order Detail(USER_DATA) | orderNo | recvWindow | Yes |
For endpoints that require authentication, you will need to provide Binance API credentials. Required credentials:
Base URLs:
Users can provide Binance API credentials by sending a file where the content is in the following format:
abc123...xyz
secret123...key
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.
When showing credentials to users:
su1Qc...8akf***...aws1Example response when asked for credentials: Account: main API Key: su1Qc...8akf Secret: ***...aws1
When listing accounts, show names and environment only — never keys: Binance Accounts:
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: abc123...xyz
- Secret: secret123...key
- Description: Primary trading account
### futures-keys
- API Key: futures789...def
- Secret: futuressecret...uvw
- Description: Futures trading account
When user provides new credentials:
TOOLS.md with masked display confirmationFor trading endpoints that require a signature:
X-MBX-APIKEY header.Otherwise, do not perform steps 3–5.
Include User-Agent header with the following string: binance-fiat/1.0.0 (Skill)
See references/authentication.md for implementation details.
Weekly Installs
210
Repository
GitHub Stars
516
First Seen
4 days ago
Security Audits
Gen Agent Trust HubPassSocketWarnSnykFail
Installed on
codex199
opencode199
gemini-cli197
kimi-cli197
cursor197
github-copilot197
飞书OpenAPI Explorer：探索和调用未封装的飞书原生API接口
23,400 周安装