Skip to main content
Your organization runs on a plan that sets two allowances: how many tokens you can use per billing period, and how many sessions you can run at the same time. Usage is tracked per organization, both allowances are readable from the API at any time, and there are no request-rate limits.

Plans

Token and concurrency allowances are subject to change, so read the live values from the API (below) rather than hard-coding the numbers in your integration.

Token usage

Tokens are consumed by the model as your agents run, and they accrue against your plan’s per-period allowance. When the allowance runs out, creating a session (or messaging a finished one, which restarts it) fails with 402 Payment Required. The error’s detail carries your limit, used, and the window_end when the budget resets. See Errors. Check your current token usage with GET /api/v2/quota/tokens:
Response

Concurrent sessions

Separately from tokens, your plan caps how many sessions can run at once. 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. GET /api/v2/sessions/quota returns your current concurrency usage:
Response
See Get quota for the field-by-field reference. At the limit, new sessions are queued and start when a slot frees up. Pass queue: false to get a 429 Too Many Requests instead.

Managing your subscription

Start a Developer subscription from the billing page in the platform dashboard; checkout is card-only. Manage your card and download invoices through the Stripe billing portal, linked from the same page. Cancelling stops the renewal: your Developer allowances stay active until the end of the current billing period, after which the organization reverts to the Free plan.

Need higher limits?

For higher token or concurrency allowances, or an Enterprise plan, contact us at support@hcompany.ai.
Last modified on September 11, 2026