Skip to main content
Limits depend on the workspace plan, operation, environment, and service configuration. Use your current usage and entitlements responses rather than historical tier tables as an integration contract.

​
Rate limits and quotas

HTTP 429 means a rate limit was applied. It does not always mean a paid upgrade is required. A service may return a separate billing or quota error, such as HTTP 402. Read the status and structured error body. Respect Retry-After when present. Not every endpoint emits the same rate-limit headers, and an omitted header does not mean there is no limit. Public verification can also be rate-limited.

​
Retry policy

Retry reads after transient failures using a bounded backoff and jitter. Retry writes only when the operation supports idempotency and you retain the same request body and idempotency key. Do not blindly retry payment, notification, or provisioning requests. A timeout leaves the outcome uncertain. Query the resulting resource where possible before creating a second operation. Treat authentication errors and invalid requests as problems to correct, not reasons for an immediate retry loop. See billing usage, entitlements, and the mint quickstart.