Frequently asked questions
A trial can be enabled for new accounts so you can confirm that the integration works and that the supported CAPTCHA types match your workflow before purchasing a package. Contact support to request trial access.
The service is designed for continuous automated workloads with monitoring and resilient infrastructure. Actual availability may vary by environment, provider, and integration, so production usage should include retry and error-handling logic.
Available payment methods depend on the payment gateway and account configuration currently enabled in the platform. Review the checkout options shown for your account or contact support when an alternative method is required.
Alternative payment methods may be arranged depending on your account and region. Contact support with the preferred method before placing the order so availability can be confirmed.
Yes. The service can be connected to scripts, browser automation, backend applications, and other supported tools. Support can help you understand the API flow, authentication, request format, and common integration issues.
Browser-based workflows can be supported through compatible extensions, integrations, or automation tools. The exact setup depends on the browser, application, and CAPTCHA type being used.
A thread represents one CAPTCHA solve that can run at the same time as other solves. For example, a package with five threads can process up to five concurrent requests before additional requests must wait for capacity.
Usage is generally controlled by concurrent thread capacity rather than a fixed daily count. You can continue sending requests while staying within the active thread limit and the terms of the selected package.
Requests above the available concurrent capacity may be delayed or rejected until a thread becomes free. Applications should handle this response safely by retrying after a short delay or by upgrading capacity.
Additional capacity can be added by purchasing another eligible package or moving to a larger package, depending on the account rules configured in the platform. Existing active service does not need to be interrupted unless the checkout flow says otherwise.