BRAHMA requests are rate limited per organization — the organization that owns the API key — on two dimensions at once, following OpenAI’s rate-limit semantics. Exceeding either limit returns 429 until the corresponding window resets.
The staging base URL is api.stage.peachdeskai.com. The production base URL api.peachdeskai.com applies once production DNS is live.

Limits

Defaults apply per organization and can be raised for your deployment — contact your PeachDesk administrator.

How TPM is counted

The TPM charge for a request is taken up front, before the completion runs:
That is, the larger of the max_tokens you request and a characters-divided-by-four estimate of your prompt. Setting max_tokens far higher than you need therefore burns TPM budget even when the completion comes back short — request only the output length you need.

Rate-limit headers

Every response — success or failure — carries your organization’s current standing in the response headers: Reset values are human-readable durations such as 1s or 6m0s. Read remaining before dispatching bursts to stay under the limit proactively rather than reactively.

The 429 response

When a limit is exceeded, the API returns 429 with a retry-after header (seconds to wait) and an OpenAI-format error body. type is tokens for a TPM breach and requests for an RPM breach:

Handling 429s: exponential backoff

Retry 429 responses with exponential backoff and jitter — honor retry-after as the floor, and randomize so concurrent clients do not retry in lockstep.
Keep max_tokens close to the output length you actually need — it is charged against TPM up front — and spread batch workloads across the minute instead of front-loading them.