Rate limits and usage
Budget requests across keys and the whole account.
Limits apply per key and per account. Creating more keys does not bypass the account limit. The console’s usage view shows effective request limits and usage by key and model.
The development gateway defaults to 60 requests per minute per key and 300 per minute per account. These are operator-configurable development defaults, not a production entitlement. Check your console for the values assigned to your account.
When limited
A 429 response includes Retry-After. Wait at least that delay before retrying. The SDKs accept either seconds or an HTTP date and wait the full delay up to 60 seconds. For a longer delay they do not retry; they raise a rate-limit error that carries the requested delay.
Keep concurrency bounded and share a queue across workers using the same key. Backoff alone cannot make an oversized workload fit a fixed limit. Ask Secnd for a limit review before a planned traffic increase.
Measure usage
Successful decisions return input-token usage and output_tokens: 0. Dashboard usage groups requests and input tokens by key and resolved model. The configured per-million input-token price supports an estimated usage cost; there is no billing-provider integration in this beta contract.
Request retries can add requests and token usage. Keep billing, request logs, and the downstream business action separate: a retried decision must not issue the same refund twice.