Skip to main content
Your organization’s plan sets two allowances: tokens per billing period, and sessions running at once. Both are tracked per organization and readable from the API. There are no request-rate limits.

Plans

Allowances may change: read the live values from the API instead of hard-coding them.

Token usage

Agents consume tokens as they run. When the period’s allowance runs out, creating a session (or messaging a finished one, which restarts it) fails with 402 Payment Required. Its detail carries limit, used, and window_end. See Errors.
Response

Concurrent sessions

A session holds a slot from the moment it leaves queued until it reaches a terminal state, including when you cancel it. Queued sessions hold no slot. See Get quota for the fields.
Response

Queued sessions

At the limit, a create doesn’t fail: it returns 201 with status queued, and the session starts on its own, oldest first, as slots free up. It then follows the normal lifecycle (queued, pending, running, terminal) and fires a webhook on every transition. Set queue: false on the create body to get a 429 instead. For batches, fire every task at once, let the platform pace them, and collect results with webhooks.

Managing your subscription

Start a Developer subscription from the billing page in the platform dashboard (card only). Manage your card and invoices through the Stripe billing portal linked from the same page. Cancelling stops the renewal: Developer allowances stay active until the end of the current period, then the organization returns to Free. For higher allowances or an Enterprise plan, contact support@hcompany.ai.