Limits and quotas

Three independent limits apply, and you hit whichever comes first: concurrency caps how many sessions you may have open at once, the monthly allowance caps actions, browser hours, and egress per calendar month, and rate limits cap requests per minute to protect the service.

Plans

	Free	Developer	Pro	Scale
Concurrent sessions	3	15	50	200
Actions / month	500	2,000	10,000	100,000
Browser hours / month	10	100	500	5,000
Egress / month	500 MB	2 GB	10 GB	35 GB
CAPTCHA solves / month	20	100	500	3,000
Max session length	30 min	2 h	6 h	12 h
Residential egress	no	yes	yes	yes
Past the allowance	hard stop	metered	metered	metered

Enterprise plans lift every cap; contact us. An action is a fetch that returned content. Blocked or failed attempts are not counted against you. Usage and credits covers checking where you stand against these limits with GET /v1/usage.

Concurrency

Concurrency counts live sessions, not requests. Exceeding it returns:

{ "detail": { "error": "concurrency_limit", "message": "plan concurrency limit reached (50) — upgrade for more", "tier": "pro" } }

The cap is enforced across your whole account, not per client or per region. The usual cause of an unexpected 429 is sessions that were never released, so check GET /v1/sessions. Release sessions in a finally block:

try {
  // ... work
} finally {
  await fetch(`https://api.tilion.dev/v1/session/${id}`, { method: 'DELETE', headers: h }).catch(() => {});
}

Rate limits

Separate from plan quotas and applied per account:

Operation	Limit
Session creates	plan-dependent, generous
Failed auth attempts	10 per minute

Exceeding a rate limit returns 429. Back off exponentially.

Credits

Metered usage past the allowance draws on a credit balance, and an empty wallet returns 402 with the machine-readable code insufficient_credits. Usage and credits covers checking the balance and redeeming codes.

Handling limits well

Read remaining from /v1/usage rather than waiting for a 402.
Cap your own concurrency below the plan limit so a burst does not lock out your other jobs.
Keep idle_timeout short, because browser hours accrue for as long as a session exists, whether or not you are driving it.
Retry 429 with backoff, never in a tight loop.

Get started

MCP

Sessions

Fetch & jobs

Content

Agent & tasks

Live view & recordings

Account

Reference

Limits and quotas

Plans

Concurrency

Rate limits

Credits

Handling limits well

​Plans

​Concurrency

​Rate limits

​Credits

​Handling limits well

Plans

Concurrency

Rate limits

Credits

Handling limits well