Skip to main content
GC AI rate-limits the API in two tiers. Inference endpoints (the model-backed calls) are limited tightly. Everything else (listing, creating, and updating projects, playbooks, files, and so on) gets a far more forgiving limit.

​
The two tiers

Each limit is a fixed 60-second window. The full quota is available at once, then resets at the end of the window.

​
What counts against the limit

Limits apply per organization, and within that per API key. GC AI checks both on every request, and whichever is exhausted first blocks it:
  • The per-organization limit is the binding ceiling. It is shared across every key the organization holds, so minting extra keys does not raise your total throughput.
  • The per-key limit keeps one integration from monopolizing the organization’s budget. It is the per-integration sub-limit beneath the organization ceiling.

​
When you exceed a limit

A throttled request returns 429 Too Many Requests:
It also carries headers describing the limit and when to retry: Honor Retry-After: wait that many seconds before sending the next request. For batch workloads, use fire-and-forget and pace your enqueues rather than retrying in a tight loop.