Please contact our plugin developers' team; they will help. We are not responsible for this tool. We only provide API for this extension.

https://antcpt.com/eng/feedback.html

It's their job to answer any questions about it.
We have no idea how it works or how it will work for you, so please address all your questions to them.

This means that your app sends garbage requests in high volumes (more than a certain amount per hour) and all of them generate errors like ERROR_WRONG_USER_KEY, ERROR_KEY_DOES_NOT_EXIST or other errors that always occur when a request is repeated.
The system automatically blocks these IPs in the firewall for a specific length of time.

Why we have to ban such IPs, and why it’s impossible to WHITELIST your IPs
We believe that properly written applications don't ever get banned. Here are some tricks to avoid bans:
1. Update your balance via API once per minute, and when it reaches zero or becomes negative, stop sending task creation requests. People sometimes forget about their scripts running on servers for months, and getting ERROR_ZERO_BALANCE forever. We block them for days using the firewall.
2. When your app starts receiving errors of any type from our API, do not ignore it. Log these errors and fix them ASAP. They usually indicate that something has broken in your automation process, and it’s worth doing some kind of log monitoring, where you immediately find out about large numbers of errors or high percentages of errors by comparison with successful results. The best situation is when you set up SMS/push notifications to go to your developers when something goes down. If you do this, they can respond rapidly and fix whatever’s damaging your business.

We don’t whitelist any of our customers’ IPs because IT WOULD DEFINITELY affect system performance and affect service quality for all our other customers. People always make mistakes and in their code, they make A LOT of mistakes. It is normal. We built our system on the bones of numerous mistakes we made ourselves, and numerous failures led to our current automated blocking system. No matter how much you spend with us, if you try to kill our API with garbage requests, you're blocked.

We do not unban IPs by request via support tickets.
If you’re blocked because of ERROR_ZERO_BALANCE errors, then your account gets unblocked automatically when you top up your balance.
For all other errors, please take the time to fix and test your applications and wait patiently for the system to unblock them when the ban expires.

You can use this tool to check your IP status at any time and (if you’re blocked) to find out when the ban will be lifted.
This tool also displays the results of ping commands from our server to your IP. If you see information about packets being successfully returned, then there should be no reason why your API requests can't reach our servers.

1. Check your hosts file at C:Windows>system32>drivers>etc>hosts . Make sure it's empty, no "anti-captcha.com" or "antigate.com" records.

2. Make sure your IP address is not present in our firewall, were we ban anyone who can't use our API properly.

3. If nothing helps, please send us ticket outputs of the following commands executed in command prompt:
a) ping anti-captcha.com
b) nslookup anti-captcha.com
c) tracert anti-captcha.com

Service stability is our first priority. Thus, if one customer is killing our API with incorrect requests, we will disable their access for the sake of other customers who don't do that and know how to utilize our API.

It doesn't matter how much the customer is spending on our service. We would rather take down access for our #1 customer than have them damaging our API.

When your IP is blocked, you can check the reason in the IP search tool. If the reason is something like an error code, you may want to search our FAQ for this code and attempt to figure out a solution for your application.
Please read the previous topic, "My IP was blocked / can't connect to API" for advice on API error management.

The limit is double the number of idle workers per queue.

For example, if there are 1000 idle workers for Recaptcha Proxy-On, then your limit is 2000. Note that numbers change every second.

You can grab the current moment worker stats from API or visually on the Dashboard by adding the "Workers Online Gauge" widget to it.

If you keep getting this error, it means your maximum bid is not high enough at the present time. Try using our service on a less busy day.

If you did set a maximum bid in settings and you're still getting this error - it means there REALLY are no idle workers; everybody is busy with high-bid tasks and there's nothing we can do about it. Try using our service on a less busy day, like Sunday.

Use this page to send captchas and retrieve text:
http://anti-captcha.com/imacros.html

Macro example:
http://anti-captcha.com/code/antigate.iim

There's also a browser plugin which supports Imacros:
http://antcpt.com/

Yes, we pay 10% of what your users spend. You need to register your app, get hold of a softId record and send it along with your captcha task requests. Good apps and the priority of our service in app settings could bring you a monthly income of thousands of dollars. Withdrawal options: BTC, LTC, ETH, Advcash.

Regarding app publicity, you have these 2 options:
1. A public app, visible in AppCenter. Must have a valid name, description, icon, website, download/purchase link. Before publishing, it must pass through moderation. Along with commissions, you also get free visitor traffic from us.
2. A private app, not published in AppCenter. Can have any description and name. Moderation not required.

Both options cost $1 to create a softId record (a simple measure to prevent spam).

To add your software, navigate to developers center.

You can "send" as many as you like, but it is preferable to refer to the number of workers currently online. All our captchas are solved by human workers, so we can't accept more tasks than there are workers.
We suggest you set the maximum threads to the number of workers multiplied by 1.5.

Example.
You want to calculate max threads for "Recaptcha Proxyless." Grab the total number of online workers with getQueueStats API method or locate it visually on your dashboard. For example, the value you see is 2000. In this case, the maximum recommended thread value is 2000 x 1.5 = 3000 threads.

No, that's not possible.
Code your application so that it first saves the captcha to your local disk (memory) and only then sends the file to our API.

Please check out this API method and make sure you read the description:

For IMAGES:
Study the documentation page please.

Complaints are accepted only for image captchas. Your complaint will be checked by 5 workers, 4 of them must confirm it positively. Only then can you get a full refund. If you have a less than 50% confirmation ratio, your future reports will be ignored.

For RECAPTCHA v2/v3:
Please study the documentation page.

For other captcha types:
No option is available to report incorrectly solved captchas of other task types.

"I've used 1,000 captchas, but registered 345 accounts, WTF?"

You should forward questions like this to your software developer. We are not responsible for the success of the actions you take with our captcha solutions.

We used to have this setting but had to remove it because it led to numerous questions from customers who were surprised at their billing stats. They set one bid in settings but got billed for another.
We have no plans to resume this feature.

Option 1. Send flag case=true in API.

Option 2.
Specify case sensitivity in API Override subsettings in API settings.

Yes, and it's called GeeTest. Please check out the documentation for more info.

Yes, we get this question sometimes – even though the links are everywhere.
It's in the Help menu -> Documentation