Does OctoBot work with Coinbase?

The OctoBot README names Coinbase as a supported exchange (README scanned 2026-09-17). We did not run the bot against Coinbase: this page reports what the public code says and what the exchange itself publishes.

Coinbase facts

CoinGecko trust score: 10 / 10 · rank 2
Country: United States
Established: 2012
24h volume (BTC, normalized): 0
Puerto Rico residents: Not verified: the eligibility page returned an access error (HTTP 403) on the check date (source, 2026-09-17)
Derivatives: Regulated futures through Coinbase Financial Markets; global perpetuals since June 2026 (source, 2026-09-17)
Official API: Yes (Advanced Trade API); futures access for U.S. territories not confirmed (source, 2026-09-17)

Exchange data: CoinGecko public API and the exchange's own endpoints, 2026-09-17. More on the Coinbase page.

What the audit says about running it live

From the OctoBot audit (2026-09-17), the controls that matter most once a live API key is connected:

Control	Verdict	Evidence
API key permissions	Partial	exchange_credentials_data.py only models api_key/secret/password/uid (CEX) or wallet_address/private_key (DEX) fields; GitHub code search for '.withdraw(' found a match only in a DEX blockchain_wallet_operators tentacle (on-chain, user-initiated), not in any CEX/CCXT order-execution path.
Orphaned stop-loss	Not verified	Order type implementations live under packages/trading/octobot_trading/personal_data/orders/ (order.py, order_factory.py, and an unread 'types' subfolder); not opened due to time/budget.
Websocket and data reconnection	Not verified	packages/trading/octobot_trading/exchanges/abstract_websocket_exchange.py (8521 bytes) exists as a dedicated websocket abstraction, confirmed via directory listing, but its reconnect/backoff/429-handling logic was not read due to time/budget.
Order rejection handling	Present	index_trading.py IndexTradingModeConsumer._rebalance_portfolio(): except (trading_errors.MissingMinimalExchangeTradeVolume, copy_errors.RebalanceAborted) as err: logs a warning/error and marks the rebalance as REBALANCING_SKIPPED instead of retrying blindly or crashing.
Position reconciliation with the exchange	Present	index_trading.py IndexTradingModeProducer.ensure_index() calls _wait_for_positions_init() and _wait_for_orders_init() at startup before rebalancing, loading real exchange positions/orders; telegram_bot.py exposes /refresh_portfolio ('Forces OctoBot's real trader portfolio refresh using exchange data').

Before you connect a key

Create the API key with trading enabled and withdrawals disabled, and restrict it to your server's IP if Coinbase 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.