Account tiers & limits

Your account controls how many solver tasks can run at once. The API keys page shows your current tier, concurrency limit, and request rate.

New account defaults

By default, new accounts start on the Free account tier. Their first completed deposit into the personal account balance moves them to Regular and raises their solver concurrency from 5 to 20 simultaneous tasks.

Account tierDescription
Free5 simultaneous solver tasks when a new account is created.
Regular20 simultaneous solver tasks after a new account's first completed personal deposit.

Pending or failed payments do not trigger the change. Signup credits, bonuses, adjustments, and refunds are not deposits. Organization deposits belong to the organization and do not upgrade a member’s personal account.

Administrators can change the presets for future registrations and deposit upgrades. The values above are the initial defaults. If an administrator assigns your tier or custom limits, later deposits preserve that assignment instead of replacing it.

Existing accounts keep their limits
This policy applies to new accounts. Accounts created before the change keep their configured limits, including any custom limits. Check your actual values on the API keys page.

One limit across personal keys

Concurrency is the number of solver tasks that are pending or processing at the same time. All personal API keys on an account share this limit. A task releases its slot when it finishes; polling /getTaskResult does not use another slot.

For example, a Free account with three keys can run 5 tasks in total across those keys. Creating another key does not add 5 more slots. Coordinate your workers around the account limit, rather than applying the full limit independently to every key.

Your requests-per-second limit is separate from concurrency. Creating tasks and polling for results both use request capacity. A concurrency increase does not automatically raise the request rate.

Request higher concurrency

  1. Open API keys in the dashboard.
  2. Choose Request higher concurrency.
  3. Enter your desired concurrent task count and explain your workload or reason.
  4. Choose Open support ticket to submit the request.

The requested count must exceed your current limit. Include enough workload detail for support to review it. If you already have an open request, follow up in that ticket instead of opening another.

Requesting a higher limit is free. Support reviews the requested amount and follows up through the ticket. Submitting a request does not immediately change your limit or purchase a subscription. Your current limit continues to apply during review.

Custom account tiers

Administrators can define tier presets, rename them, and assign them to accounts. Free and Regular are the initial names for the new account defaults; the tier name you see can change. Administrators can also configure an individual account’s limits. Always use the numeric values shown in the dashboard when configuring your integration.

Product and subscription limits

Account concurrency covers solver tasks. Solver subscription or task-specific caps, Browser API sessions, Capium licensing, Fingerprint API limits, and Data API execution limits follow their own service or plan settings. An account tier change does not assign or change those subscriptions.

Organization keys use their organization’s balance and settings. The Free-to-Regular personal account policy does not replace organization plans or limits.

When the limit is reached

/createTask can return ERROR_CONCURRENT_LIMIT or ERROR_MAX_TASKS_REACHED when no account task slot is available. Keep polling existing tasks, wait for a completion, and retry with a short delay. Avoid retrying in a tight loop. ERROR_RATE_LIMITED means you must reduce your request rate.

See Errors for the full reference and Getting the result for polling guidance.