Skip to main content

CaptchaAI

Written by Dmitry

CaptchaAI is a captcha-solving service that can route challenge-solving through your own proxy, so the captcha is solved from the same IP that loads the target page. This is required when the target site enforces IP matching (e.g. Cloudflare, Datadome). In this guide, we'll walk through how to use your Gsocks private proxies with CaptchaAI.

Proxy support at a glance:

- Supported captcha types: reCAPTCHA v2 and Turnstile. (reCAPTCHA v3 is not supported with proxies.)

- Supported protocols: HTTP, HTTPS, SOCKS5.


1) Registration

You can create a CaptchaAI account

2) Enable proxy usage

Proxy usage in CaptchaAI is disabled by default. Turn it on in your CaptchaAI account settings: https://captchaai.com/config

3) Get your Gsocks private proxy details

In your Gsocks account, open the Private tab and select the port you want to use. You'll need its details in the format ip:port:login:pass:

IP: <your proxy IP>

Port: <your proxy port>

Username: <your proxy login>

Password: <your proxy password>

You can copy them directly from the port in your Private tab.

4) Add the proxy to your CaptchaAI request

CaptchaAI takes the proxy as two parameters in your solve request (in.php or the matching method endpoint):

proxy — your proxy address, as username:password@host:port

proxytype — one of: HTTP, HTTPS, SOCKS5

Important: the proxy value must not include http://, https://, or a trailing slash.

5) Send the request

Example — reCAPTCHA v2 with a Gsocks private proxy (SOCKS5):

{
"key": "YOUR_API_KEY",
"method": "userrecaptcha",
"googlekey": "YOUR_SITE_KEY",
"pageurl": "https://example.com/login",
"proxy": "username:[email protected]:10000",
"proxytype": "SOCKS5"
}

Replace username, password, IP and port with your actual Gsocks private proxy details.

6) Retrieve the result

After submitting, poll res.php as usual to get the solution. For Turnstile, you may need to pass json=1 when retrieving to get structured fields.

Notes & best practices

- Private proxies are a great fit here: each one is a dedicated static IP, so the solving IP stays consistent.

- Use the proxy only when the target site requires IP matching. Otherwise, omit it for the best success rate and lowest latency.

- Do not use proxies with reCAPTCHA v3 — it's not supported and success rates drop.

- If you get proxy-related failures, confirm the proxy is active in your Gsocks account and can reach the target site's domain.

Further reading (CaptchaAI docs)

- reCAPTCHA v2 Enterprise (host:port example): https://docs.captchaai.com/guides/recaptcha-v2-enterprise/


Do you have more questions or want a trial? Contact Gsocks support at [email protected].

Did this answer your question?