Binance API
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Binance Spot API helper that uses sensitive trading credentials and local operational memory, but the artifacts disclose those behaviors and require testnet-first use plus explicit confirmation before production orders.
Install only if you intend to let the agent help with Binance Spot workflows. Use testnet first, restrict API-key permissions, never paste secrets into chat, require explicit confirmation before any production order, and periodically review the local ~/binance memory files.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used with production keys, the agent can help submit real Binance Spot orders after confirmation.
The skill documents a path from test orders to real production order placement, which is high-impact, but it explicitly requires user confirmation.
Replace `/api/v3/order/test` with `/api/v3/order` only after user confirmation for production activity.
Keep testnet as the default, require clear per-order confirmation for production trades, and review symbol, side, quantity, price, and account before execution.
A Binance API key with trading permissions can read account data and place or manage orders.
The skill needs Binance credentials for signed account and trading endpoints; this is expected for the purpose and is disclosed.
`BINANCE_API_KEY` and `BINANCE_API_SECRET` for signed Spot requests
Use least-privilege API keys, prefer testnet keys during setup, enable IP restrictions if available, and never paste secrets into chat or repository files.
Local memory may contain sensitive trading preferences, symbols, incidents, and workflow history, and future sessions may rely on it.
The skill stores persistent operating mode, action scope, symbols, and inferred preferences that can influence future Binance workflows.
`~/binance/memory.md` ... `Allowed actions: market-data | account-read | trading` ... `Stable user preferences inferred from behavior`
Keep secrets out of these files, periodically review or delete ~/binance contents, and confirm that stored defaults still match your intended trading limits.