Skip to main content
Baseten enforces per-API-key rate limits on the management API. The limits protect shared infrastructure, such as the build queue, from bursty automation.

Limits

Default limits vary by endpoint. Endpoints used for frequent status polling have higher limits than most other management operations. Baseten can adjust these defaults based on usage. Handle 429 responses using retry_after so your automation adapts to the limit that applies to each request. Contact support to confirm the limits for your workload or request an increase. The following endpoints have specific limits: Baseten tracks usage separately for each API key and endpoint. If your organization has a custom limit for an endpoint, that limit takes precedence over the default.

Rate-limited responses

A request over the limit returns 429 Too Many Requests:
retry_after is the number of seconds until the current rate-limit window resets. Wait at least that long before retrying.

Retry handling

For CI pipelines or scripts that call the management API in a loop, handle 429 explicitly:
Back off on retry_after instead of retrying immediately. A tight retry loop wastes API calls; the server rejects every request until the window resets.

Request higher limits

If your workload needs sustained throughput above the default limits, contact support to request per-endpoint increases for your organization.