# Abuse controls and quotas

The management API applies per-environment token buckets to resource creation and metadata fetches. The currently implemented capacities refill evenly over the stated period; they are not calendar reset counters.

| Action               | Capacity and refill period |
| -------------------- | -------------------------- |
| Create organizations | 200 per day                |
| Fetch SAML metadata  | 30 per minute              |
| Create portal links  | 100 per hour               |

A depleted quota returns HTTP 429 [`rate_limited`](/errors/rate_limited/) with `Retry-After`. Wait at least that interval before retrying and avoid parallel retry storms. Separate plan entitlements still return [`plan_limit_reached`](/errors/plan_limit_reached/); waiting for a bucket refill does not increase the plan's connection allowance.

Quota and request rate-limit cache failures fail open so a cache outage does not make these availability controls refuse every request. Therefore these sizes are not a durable exact ceiling under faults, and they do not replace authorization or plan checks. API body-size limits are separate and return [`payload_too_large`](/errors/payload_too_large/).

## Sign-up checks

New-account sign-up refuses disposable email domains with HTTP 400 [`email_disposable`](/errors/email_disposable/). Use an address you keep. Where Turnstile protects sign-up, its challenge token is required and missing or refused tokens return `parameter_invalid`.

Sign-ups on standby are paused; an unavailable primary challenge also returns HTTP 503 [`sign_up_paused`](/errors/sign_up_paused/). Existing-account authentication remains separate and still requires its normal factors. See [standby behavior](/trust/standby/) and [dashboard security](/get-started/dashboard-security/).
