Solve hCaptcha in your stack.
Practical guides for getting a real hCaptcha token back into your pipeline. Read the sitekey, call the API, inject the token, then continue.
- Python hCaptcha solverpip install vanishcaptcha, with sync, asyncio, and plain-requests examples.
- Solve hCaptcha in SeleniumThe Python flow, with the token written into the widget before submit.
- hCaptcha solving for web scrapingThe full pipeline with a Python example, no browser required.
- Solve hCaptcha in PlaywrightPython and Node, with the token written into the page before you click submit.
- Solve hCaptcha in PuppeteerThe Node.js flow, with the token written into the page before submit.
- Node.js hCaptcha solverThe one-call npm SDK path, plus a zero-dependency fetch example.
- Solve hCaptcha in GoA complete net/http client, no SDK needed.
- Solve hCaptcha in ScrapyDetect the gate in a callback, or wrap the flow in downloader middleware.
- hCaptcha solving for AI agentsCall the solver as a tool inside an agent loop.
Every guide follows the same four steps
- Read the sitekey from the page. Each guide shows the one-liner for its stack.
- Request a token with POST /v1/solves, passing the sitekey and page URL. Block with ?wait= or let the SDK poll.
- Write the token into the form’s hidden h-captcha-response field, and the g-recaptcha-response field when the page has one.
- Submit and move on. Tokens are single-use and expire in about two minutes, so mint them right before submission.
If you drive a browser, start with Selenium, Playwright, or Puppeteer. If you make plain HTTP requests, the web scraping guide stays off a browser, and Scrapy packages that as a callback. Python and Node.js are the shortest path to a working call. The AI agents guide wraps the same call as a tool.
Every guide targets hCaptcha: regular, invisible, and enterprise rqdata. The endpoint reference is the API reference. The Chrome extension is the no-code path for browsing.