Limits and retries
Check active plan and usage limits through the account or GET /v1/billing/limits. Model usage, app counts, storage, and request throttling are different constraints.
Handle a refused request
Section titled “Handle a refused request”Read the HTTP status and response body. For a 429 response, honor Retry-After when supplied and use bounded backoff. A 403 permission error, missing route, or exhausted allowance requires a different correction; repeated retries will not fix it.
Bound automation
Section titled “Bound automation”Set a maximum retry count and a deadline in your client. Keep read polling infrequent enough for the task. Before retrying a mutation, establish whether the original operation succeeded and whether that endpoint supports the idempotency behavior you need.
The previous documentation’s fixed per-minute and publish-velocity numbers are not verified for the current service. No universal request-rate, spend-cap enforcement, or free-retry guarantee is implied by the presence of quota fields on a key.