Best practices

#Send what the user sees

• Send the full task text. Use the sentence from the challenge, for example Select all images with buses, not only bus. The models answer best with the full sentence.
• Send the right grid. 3x3 or 4x4 for a whole grid in one picture, 1x1 for single tiles that appear after a click.
• Send clean pictures. Send the picture as the page shows it, as base64 without a data: prefix. Stay below 4.5 MB per request.
• Match the answer to the tiles. The answer lists tiles left to right, top to bottom. Count the tiles on your page before you click.

#Poll with care

• Poll each job about once per second. Do not poll faster. Polls have their own rate limit.
• Stop after about 30 seconds and create a new job.
• Treat error 14 as normal, not as a failure. See Errors.

#Retry the right errors

#Expect more than one round

A reCAPTCHA challenge can ask several times. Google can show a new grid after a wrong or a half answer. Build your script so that it submits an answer, checks what the page does, and asks again with the new pictures. On Google's public demo, 99.7 % of user sessions got a token within up to 3 fresh challenges (299 of 300 sessions, 17 October 2026, one data-center IP). Plan for up to 3 challenges, not one.

#Look like a normal visitor

Captchas often depend on how the visit looks. These steps lower the number of challenges and the number of rejected answers:

• Use good proxies. Datacenter IP addresses can get more challenges than residential ones. Use one stable IP address for the whole session. Do not change the IP between the page load and the submit.
• Use a realistic browser. A CloakBrowser session has a real-looking fingerprint. Plain headless automation is easier to spot.
• Match time zone and language to the IP address of the proxy.
• Wait like a person. Pause between clicks. The extension has delay settings.
• Keep cookies. A persistent browser profile keeps cookies between runs.

We have no numbers for how much each step helps. It depends on the site.

#Send feedback

When you solve reCAPTCHA through the API, tell us whether Google accepted the answer with POST /v1/feedback. It is free, optional and helps us improve the models. The browser extension does this for you.

#Keep inside the limits

• Check GET /v1/status before a large batch.
• Keep a counter of open jobs.
• Use one key per project, and keep keys on the server.
• Read Rate limits and quotas for the numbers.

#Use the service for legitimate purposes

Use Solvecha for accessibility, for testing your own sites and in places where you have permission. Fraud, spam, account takeover and bypassing protection without permission are forbidden. We can block keys that break the Acceptable Use Policy.