The short answer

On raw crypto API limits in 2026, Binance uses a weight-based budget of 6,000 request-weight per minute per IP while Coinbase Advanced Trade throttles a flat 30 requests/second on private endpoints and 10/second on public ones. Binance gives more raw throughput for polling-heavy agents; Coinbase is simpler to reason about. Neither charges an API fee.

On raw API limits for crypto trading in 2026, Binance and Coinbase Advanced Trade split on how they meter you: Binance uses a weight-based budget of 6,000 request-weight per minute per IP, while Coinbase throttles by a flat 30 requests/second on private (authenticated) endpoints and 10 requests/second on public ones. Binance gives more raw throughput for a polling-heavy agent; Coinbase's flat per-second model is simpler to reason about and its per-user private limit is not shared across an IP. Neither charges an API fee; cost is trading commission, not access. Verify both before building.

TL;DR

Dimension Binance Spot API Coinbase Advanced Trade API
API fee $0 $0
Rate-limit model weight-based budget flat requests/second
Private (authenticated) limit 6,000 request-weight/minute per IP 30 requests/second per user
Public limit shares the weighted IP budget 10 requests/second per IP
WebSocket yes yes (connection + message limits)
Over-limit response HTTP 429, then 418 IP ban HTTP 429 with Retry-After
Metering basis per IP private per user, public per IP

Binance and Coinbase figures verified 2026-05-25 against official docs. This page covers raw API limits and the trading surface; it is not investment, custody, or jurisdiction advice.

Rate limits side by side

The two exchanges meter differently, and the difference matters more than the headline numbers:

  • Binance runs a weight-based budget. Each endpoint costs a "weight," and the REQUEST_WEIGHT limit is 6,000 every minute, enforced per IP (the limits are IP-based, not API-key-based). Heavy endpoints, especially ones that touch many symbols, cost more weight per call, so a single "expensive" call can consume what several light calls would. Every response carries an X-MBX-USED-WEIGHT header so you can track your remaining budget; exceeding it returns HTTP 429, and repeatedly ignoring 429s escalates to an automated IP ban (HTTP 418) (verified 2026-05-25).
  • Coinbase Advanced Trade runs a flat per-second model. Private (authenticated) REST endpoints are throttled per user at 30 requests/second; public (unauthenticated) endpoints are throttled per IP at 10 requests/second. WebSocket connections are limited separately. Over-limit calls return HTTP 429 with a Retry-After header telling you how long to back off (verified 2026-05-25).

The structural consequence: Binance's weighted budget rewards designing around endpoint cost (batch where you can, avoid all-symbol calls in a tight loop), while Coinbase's per-second cap is simpler to reason about but harder to burst against. Because Binance meters per IP, multiple bots behind one IP share the budget; Coinbase's private limit being per user means each authenticated key gets its own 30/second.

Cost and the trading surface

Neither exchange charges for API access. The cost is trading commission, which is tiered by volume and (on Coinbase) by which product surface you use, not by API calls. Both expose spot trading, order placement and cancellation, balances, and historical data through REST plus a WebSocket streaming interface for live market data and order updates.

The practical framing: for an agent that polls order books and places frequent orders, Binance's 6,000 weight/minute gives more headroom for a single IP, provided you keep heavy multi-symbol calls out of the hot loop. For an agent that wants a clean per-user budget it does not have to share across an IP, Coinbase's 30/second private limit is the cleaner model.

Jurisdiction is the real decision

Rate limits are rarely what actually picks the exchange; availability is. Binance and Coinbase differ sharply by jurisdiction (Binance.US is a separate entity from Binance global with its own API and availability; Coinbase availability varies by region). For a builder in the EU, check which entity and which products are accessible to you before optimizing rate limits, the same way US-listed broker APIs gate on account eligibility. None of this is custody or regulatory advice; confirm eligibility with the exchange directly.

Decision guidance

  • Polling-heavy agent on a single IP, want maximum throughput: Binance, with its 6,000 weight/minute budget, provided you design around endpoint weight.
  • Want a per-user budget you do not share across an IP: Coinbase Advanced Trade, 30 requests/second per user on private endpoints.
  • Simpler rate-limit mental model: Coinbase's flat per-second cap is easier to reason about than Binance's weighted budget.
  • Either way: treat the exchange feed and order surface as untrusted at the boundary, and confirm jurisdictional availability of the specific entity before building.

Connects to

References

  • Binance. "Rate limits" and "LIMITS." developers.binance.com/docs/binance-spot-api-docs/rest-api/limits, verified 2026-05-25 (REQUEST_WEIGHT 6,000/minute per IP; X-MBX-USED-WEIGHT header; HTTP 429 then 418 IP ban).
  • Coinbase Developer Platform. "Advanced Trade API Rate Limits." docs.cdp.coinbase.com / docs.cloud.coinbase.com/advanced-trade, verified 2026-05-25 (private 30 req/s per user, public 10 req/s per IP, HTTP 429 with Retry-After).
  • Coinbase Developer Platform. "Advanced Trade WebSocket Rate Limits." docs.cdp.coinbase.com/coinbase-app/advanced-trade-apis/websocket, accessed 2026-05-25 (separate WebSocket connection and message limits).

Frequently asked questions

Binance vs Coinbase API: which has the better rate limits?
They meter differently. Binance allows 6,000 request-weight per minute per IP (weight-based), and Coinbase allows 30 requests/second per user on private endpoints and 10 requests/second per IP on public ones. Binance gives more raw throughput for a single IP; Coinbase's per-user model is simpler and not shared across an IP (verified 2026-05-25).
Is the Binance or Coinbase API free?
Both are free to access. There is no API fee; the cost is trading commission, which is tiered by volume and product, not by API calls.
What happens when I exceed the rate limit on Binance or Coinbase?
Binance returns HTTP 429, and repeatedly ignoring 429s escalates to an automated IP ban (HTTP 418). Coinbase returns HTTP 429 with a Retry-After header indicating how long to back off. Implement exponential backoff on both.
Which exchange API should an EU builder choose, Binance or Coinbase?
Decide jurisdiction first. Binance.US is a separate entity from Binance global with its own API and availability, and Coinbase availability varies by region. Confirm which entity and which products are accessible to you before optimizing rate limits. This is not custody or regulatory advice.