Audits › wardbradt/peregrine › Coinbase
Bot × exchange
Does peregrine work with Coinbase?
The peregrine README does not name Coinbase directly, but it names ccxt, the exchange library that ships a Coinbase adapter. Whether the bot's own code handles Coinbase's rules (symbols, order types, rate limits) is not something a README scan can tell. 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
Audit scheduled
When the peregrine 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 Coinbase allows it.
- Start in paper or dry-run mode if the bot has one (the README does not mention one).
- 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.