Audits › Ganador1/FenixAI_tradingBot › Binance.US
Bot × exchange
Does FenixAI_tradingBot work with Binance.US?
The FenixAI_tradingBot README does not name Binance.US directly, but it names ccxt, the exchange library that ships a Binance.US adapter. Whether the bot's own code handles Binance.US's rules (symbols, order types, rate limits) is not something a README scan can tell. We did not run the bot against Binance.US: this page reports what the public code says and what the exchange itself publishes.
Binance.US facts
- CoinGecko trust score
- 9 / 10 · rank 14
- Country
- United States
- Established
- 2019
- 24h volume (BTC, normalized)
- 0
- Tradable pairs
- 265
- Quote currencies
- BTC, USD, USDC, USDT
- Order types (BTCUSD)
- LIMIT, LIMIT_MAKER, MARKET, STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT
- Markets
- spot only: no futures, no margin
- Puerto Rico residents
- Accepted, in writing (source, 2026-09-17)
- Fees
- 0 % maker / 0.02 % taker on spot (source, April 2026)
- Official API
- Yes: REST and websocket, HMAC-signed private endpoints (source, 2026-09-17)
Exchange data: CoinGecko public API and the exchange's own endpoints, 2026-09-17. More on the Binance.US page.
What the audit says about running it live
Audit scheduled
When the FenixAI_tradingBot audit is finished, this section will show the verdicts for API key permissions, orphaned stops, reconnection, order rejection handling and position reconciliation: the five controls that matter most once a live key is connected.
Before you connect a key
- Create the API key with trading enabled and withdrawals disabled, and restrict it to your server's IP if Binance.US allows it.
- Start in paper or dry-run mode if the bot has one (the README mentions it).
- Decide the maximum loss per day before the first order and check the bot can enforce it: see the circuit breaker control. If it cannot, the watchdog enforces it from outside with a read-only key.