Every enforced size, count, timeout and cap on the platform. Where a field has a default and a range, both are given. None of these is configurable per workspace.

Agents

There is no size limit on an agent config or on an inline definition sent with a call request.

FAQs

Tools

Code sandbox

Agent tasks

See task errors and limits.

Calls and chats

Files

A file over a limit marked stored is kept for you, and the agent is told why it cannot read it. Nothing is truncated. See vision and images.

Batches

Email from_name is at most 200 characters; one email send request names up to 10,000 recipients. An analysis backfill takes up to 100 call ids.

Observability and webhooks

Names and credentials

Pagination

List endpoints take limit and offset and return { items, has_more, limit, offset }, with no cursor and no total. See pagination. Two catalog endpoints differ: GET /v1/catalog/voices pages with page and returns total_count, and model search (GET /v1/catalog/models) takes limit up to 50 (default 20) with a cursor.

Limits that do not exist

  • No API rate limit. No per-token, per-workspace or per-IP quota and no 429 from Talqing. A 429 you see was relayed from one of your providers.
  • No workspace concurrency cap. Only a batch’s own max_concurrency or draft_concurrency limits parallelism, per batch.
  • No spend cap. The only stop is a credit balance of zero; low_balance_threshold ($2) only warns. See pricing and credits.