NoneCap
hCaptcha tokens for developers, Enterprise rqdata included.
NoneCap is a captcha solver built around hCaptcha, Enterprise rqdata sitekeys included. It returns valid tokens for teams automating or testing flows that sit behind hCaptcha, with SDKs for Node.js and Python.
Use SocksNode with NoneCap
Four steps. Keep one sticky IP while you solve and submit, so the site sees one visitor.
- 1
In your scraper or browser automation, open the proxy settings for the requests that reach the protected page.
- 2
Choose HTTP or SOCKS5. Host: global.socksnode.com. Port 10000 (HTTP) or 12000 (SOCKS5) keeps one IP for the session.
- 3
Paste your proxy username and password from the SocksNode dashboard, with a session ID so the IP holds, for example USERNAME-country-us-session-a1b2c3d4-lifetime-10.
- 4
Load the page, send its site key and URL to NoneCap, and submit the token it returns from the same session.
Proxy settings for solving captchas
- Host
- global.socksnode.com
- Port
- 10000 (HTTP) · 12000 (SOCKS5)
- Username
- USERNAME-country-us-session-a1b2c3d4-lifetime-10
- Password
- ••••••••
When a site checks that the solver's IP matches yours, pass the same SocksNode proxy to the solver as well.
Why NoneCap and SocksNode work well together
Fewer challenges in the first place
A real home IP from SocksNode meets fewer hCaptcha challenges than a datacenter range, so the solver only handles what is left.
One address from token to submit
A sticky SocksNode session keeps the same IP while the token is solved and the form is submitted, which is what sites that tie a token to an address expect.
Solve through the same proxy
Where a site compares the address that solved the captcha with the one that loaded the page, NoneCap can work through the same SocksNode session you browse with.
Example: an hCaptcha form from a German home IP
Load the page, get the token and submit the form, all from one German address.
- 1
In the SocksNode dashboard, generate a sticky proxy: host global.socksnode.com, port 10000 (HTTP), username USERNAME-country-de-session-4a7e22b9-lifetime-10.
- 2
Open the page through that session and read the hCaptcha sitekey, plus rqdata if the site uses Enterprise.
- 3
Send the sitekey, the page URL and rqdata to NoneCap with the Node.js or Python SDK, and wait for the token.
- 4
Put the token in h-captcha-response and submit the form through the same session.
Questions about NoneCap and SocksNode
Do I need a proxy to use NoneCap?
Not always. Use one when the site checks that the address solving the captcha matches the address that loaded the page, and when you need the page from a particular country.
What about Enterprise sitekeys?
NoneCap handles Enterprise rqdata sitekeys. Pass the rqdata value along with the sitekey and the page URL.
Which SocksNode proxies work best here?
Rotating residential on a sticky port, so one session keeps one home IP from the first request through to the submit. Datacenter is cheaper but meets more challenges.
Other partners
Build a tool for proxy users?
List your product here and link to us from yours. Send us your site and a line on what it does.