Usage and Limits

API-key usage is tracked separately for new Technical Sessions and workflows. Limits come from the issued key record; do not assume every plan has the same values.

Inspect current usage

GET /v1/api/usage/status returns source-derived fields including:

• org_id, key_id, owner, and plan
• sessions_used, session_limit, and sessions_remaining
• workflows_used, workflow_limit, and workflows_remaining
• limits.requests_per_minute
• is_unlimited and the current monthly window

The route currently lacks a response model in OpenAPI.

Enforced limits

• Request-rate exhaustion returns 429 with API request rate limit exceeded.
• Session exhaustion returns 429 with API session limit reached for this billing period.
• Workflow exhaustion returns 429 with API workflow limit reached for this billing period.

The backend decrements neither counter on a failed generation; it meters successful API session and workflow activity. Provider rate limits can also return 429, with a different message. Use the response detail when present and avoid treating every 429 as the same recovery window.

Retry policy

Retry transient provider limits with bounded exponential backoff. Do not automatically retry exhausted monthly session or workflow limits. Read usage status and request a limit change through support when necessary.