The short answer

For a crypto trading bot in 2026, Binance vs Coinbase vs Kraken comes down to fees, rate limits and jurisdiction. Binance has the lowest fees (0.10% maker and taker, 0.075% with BNB) and the largest bot ecosystem, but US users get the separate Binance.US. Kraken publishes its full schedule: 0.40% maker and 0.80% taker at entry, plus documented rate limits. Coinbase wins US regulatory standing but shows its fees only after sign-in.

For a crypto trading bot in 2026, Binance vs Coinbase vs Kraken comes down to fees, rate-limit model, and jurisdiction. Binance wins on cost, with a standard 0.10% maker and taker spot fee (0.075% with BNB) and the deepest bot ecosystem, but US access runs through the separate Binance.US. Kraken publishes the most complete picture: an entry tier of 0.40% maker and 0.80% taker that falls with volume, documented REST rate limits, and WebSocket plus FIX connectivity. Coinbase wins on US regulatory standing, but it no longer publishes its Advanced fee table or its REST request quotas. Cheapest bot fills favor Binance; US compliance favors Coinbase or Kraken. Model your real fee drag in the Data-Vendor TCO Calculator before committing.

TL;DR

Dimension Binance Coinbase Kraken
Entry spot fee (maker / taker) 0.10% / 0.10% (0.075% with BNB) shown after sign-in, not published 0.40% / 0.80%
Rate-limit model 6,000 request-weight/minute per IP REST quota not published; WebSocket 8 connections/second per IP call counter per API key, decaying by tier
US access via Binance.US (separate) full US regulated US available
Bot ecosystem largest mature strong
Streaming WebSocket WebSocket WebSocket and FIX

Fees and rate limits checked against each exchange's documentation on 2026-10-18. Binance and Kraken lower fees at higher 30-day volume. Verify before building.

The three-way split

These exchanges optimize for different things. Binance optimizes for cost and breadth: the lowest standard fees, the most pairs, and the largest third-party bot ecosystem. Coinbase optimizes for US regulatory standing, and keeps its fee table and REST quotas out of public view. Kraken sits between them: a fully published fee and rate-limit schedule, low-latency WebSocket and FIX connectivity, and clean US availability.

For an automated strategy, three things dominate: how much fees eat per round trip, how the rate limits constrain your request pattern, and which jurisdiction you can actually trade from. Take them in order.

Fees: Binance wins, by a lot

Fees are the decisive variable for any bot doing volume. Binance charges regular users (under $1,000,000 of 30-day volume) a standard 0.10% on spot trades for both maker and taker, dropping to 0.075% with the BNB fee discount. Kraken now sets one tier from the best of your 30-day spot volume, 30-day futures volume and assets on platform; its entry tier is 0.40% maker and 0.80% taker, falling to 0.22% / 0.38% from $10,000 of 30-day spot volume and 0.15% / 0.30% from $50,000. Coinbase no longer publishes its Advanced fee table: its help centre tells you to sign in to see your tier, and every order preview shows the fee before you submit.

The gap compounds. On $50,000 of taker volume in a month, Binance's 0.10% costs $50; Kraken's 0.30% taker rate at its $50,000 tier costs $150, and its 0.80% entry rate would cost $400. For a high-turnover bot, fee drag alone can decide whether a marginal edge survives, which is why Binance dominates cost-sensitive automated trading.

Rate limits: three different models

The exchanges constrain request volume differently, which shapes how you architect a bot:

  • Binance uses a weight-based system: each endpoint costs a weight against a budget of 6,000 request-weight per minute per IP, alongside order limits of 100 orders per 10 seconds and 200,000 per day. You plan around endpoint weights rather than a flat call count.
  • Coinbase Advanced Trade no longer publishes REST request quotas; its rate-limit page now redirects to the API overview. Until at least May 2026 its documentation gave 30 requests/second per user on private endpoints and 10 per IP on public ones. What it does publish is the WebSocket limit: 8 connections and 8 unauthenticated messages per second per IP.
  • Kraken gives each API key a call counter. Most calls add 1 and ledger or trade-history calls add 2; the counter caps at 15 on the Starter tier and 20 on Intermediate and Pro, and decays by 0.33, 0.5 or 1 per second respectively. Order placement and cancellation run on a separate trading-engine limiter.

For polling-heavy designs, Kraken's documented counter is the easiest to plan against: a Starter key that averages fewer than one call every three seconds never throttles. Binance's weight budget gives the most raw headroom on a single IP. On Coinbase, build backoff around rate-limit errors, because there is no published quota to plan against. For streaming-first designs, all three reward subscribing over polling.

Jurisdiction decides which of the three you can use

The cheapest venue is worthless if you cannot legally trade on it, so geography filters the field before fees do. Binance's main exchange excludes US users, who fall back to the thinner Binance.US. Coinbase is a US-regulated exchange and the safest compliance default. Kraken also serves US users and is the common alternative for those who want a published fee schedule and FIX access on a regulated venue. A non-US bot keeps all three on the table; a US bot is really choosing between Coinbase and Kraken. Check your own jurisdiction first.

Decision guidance

  • High-turnover bot, fees dominate, non-US or Binance.US viable: Binance. The fee gap is decisive.
  • US-first, regulatory standing matters most: Coinbase. Confirm your fee tier after sign-in before you size the strategy.
  • Want a fully published fee and rate-limit schedule on a US-available venue: Kraken.
  • Polling-heavy architecture: Kraken's documented counter or Binance's weight budget; on Coinbase, only with backoff built in.
  • Streaming-first high-frequency: Kraken's WebSocket and FIX, or Binance's depth.

Put your turnover through the math

The published fee spread, from 0.075% (Binance with BNB) to 0.80% (Kraken's entry-tier taker rate), only tells you the order; your trade count tells you the magnitude. At the same monthly volume the bill can differ several-fold, which is enough to flip a strategy from profitable to underwater. Run your expected volume and frequency through the Data-Vendor TCO Calculator and size positions by edge uncertainty, so fee drag does not quietly cancel a thin edge.

Connects to

Sources

  • Binance, "Trading Fee Rate," binance.com/en/fee/trading (accessed 2026-10-18): regular user 0.100% maker / 0.100% taker, 0.075% with BNB.
  • Binance, Spot API exchangeInfo rate limits, api.binance.com/api/v3/exchangeInfo (accessed 2026-10-18): REQUEST_WEIGHT 6,000 per minute; ORDERS 100 per 10 seconds and 200,000 per day.
  • Kraken, "Fee Schedule," kraken.com/features/fee-schedule (accessed 2026-10-18): cross-platform tiers, Tier 1 0.40% maker / 0.80% taker.
  • Kraken, "Spot REST Rate Limits," docs.kraken.com/exchange/guides/rest/ratelimits (accessed 2026-10-18): call counter maximum 15/20/20 and decay 0.33/0.5/1 per second for Starter/Intermediate/Pro.
  • Coinbase, "Coinbase Advanced fees," help.coinbase.com (accessed 2026-10-18): current rates shown after sign-in.
  • Coinbase Developer Platform, "Advanced Trade WebSocket Rate Limits," docs.cdp.coinbase.com (accessed 2026-10-18): 8 connections and 8 unauthenticated messages per second per IP.

Frequently asked questions

Which crypto exchange API has the lowest fees for a trading bot?
Binance, by a clear margin where its main venue is available. Standard spot is 0.10% maker and taker, falling to 0.075% with the BNB discount, against Kraken's entry tier of 0.40% maker and 0.80% taker. Coinbase shows its Advanced rates only after sign-in, so confirm your tier there before comparing (checked 2026-10-18).
Can US traders use the Binance API for a bot?
Not the main exchange, which excludes US users; US access is the thinner Binance.US. So a US bot is really choosing between Coinbase, the safest regulated default, and Kraken, the lower-fee regulated alternative. Confirm state-level availability before you commit to either.
How do the three rate-limit models differ?
Binance uses a weight budget of 6,000 per minute per IP, so you optimize which endpoints you hit. Kraken gives each API key a call counter that caps at 15 to 20 and decays by 0.33 to 1 per second depending on verification tier. Coinbase no longer publishes Advanced Trade REST quotas; it documents WebSocket limits of 8 connections and 8 unauthenticated messages per second per IP.