Quotas and keys

Client daily limits apply to POST /v1/jobs and POST /v1/stream (UTC day). Hosted chat uses the same stream path and counts against the same client row.

Limits

  • Client daily limit — all traffic for the API key / tenant.
  • Per-user daily requests — external_user_id meter when configured.
  • Per-user priority — when options.priority is priority and a priority cap is set.
  • Per-user Deep Dive — when Deep Dive is requested and a Deep Dive cap is set.
  • Feedback routes do not consume quota.
  • Deep Dive also has its own policy flag on the client row (off by default for new partners).

GET /v1/usage (and hosted /chat/usage) returns those three dimensions as used / limit / remaining for the current UTC day. See API reference for the payload shape. The conversation “context usage” meter in the hosted UI is a token-window hint, not this API quota.

Rotate

Rotating the secret key invalidates the previous plaintext immediately. Update your backend config. The hosted page does not use that key, so SKU 2 chat keeps working until you rotate the handoff kid (which invalidates outstanding hosted session tokens).

POST /v1/hosted-session does not consume the client daily quota.

Disable

Revoking the client sets enabled = 0. API Bearer calls fail. The tenant hostname 404s until the row is enabled again. Disabling one hosted user (from /account) blocks only that person.