Sume API requests per minute by plan: write and read limits

Sume's API limits requests per minute by plan: writes are 120 (Free), 300 (Pro), 600 (Startup) and 1200 (Scale), and reads are 40 times writes. Enterprise is contract-based and behaves like Scale until limits are provisioned.

These are request limits, separate from how many generations run at once, which admission control sets.

The table

Numbers are from the Sume authentication page (read 2026-10-03). Prices of the plans themselves are on the API pricing page.

What counts as a read

Any GET or HEAD is a read, and so are /v1/generation/admission-preview and the MCP endpoint. Everything else, including every job submit, is a write. That makes polling cheap: one status check costs a read, and a read is a fortieth of a write.

The multiple comes from a deployment setting, so verify it from the headers instead of assuming it. A 429 carries retry-after and an error.details.scope of read or write.

curl -s -D - -o /dev/null https://api.sume.com/v1/me \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | grep -iE "^(ratelimit-|retry-after)"

Plan for the write limit

A burst of submits is limited by writes long before polling is limited by reads. At Free, 120 writes a minute is two per second, though the one running generation slot is the tighter limit in practice. See polling budgets by plan for the read side.