If your scraper or test suite stopped at an hCaptcha widget sometime in the last two years, the service you used to send it to may be part of the problem.

2Captcha removed hCaptcha from its API documentation around the start of 2025. CapSolver's hCaptcha documentation page has returned a 404 since January 2025. If your code was written against either one for hCaptcha, you need a different place to send those jobs.

This post covers how token-based solving works, what to do when the site is yours, and one way to wire a solver into a script.

First: is it your own site?

If the hCaptcha widget sits on an app you control and you only need your end-to-end tests to get past it, you don't need a solving service. hCaptcha publishes test keys for this. In your test environment, set the widget's sitekey to 10000000-ffff-ffff-ffff-000000000001 and your server's secret to the matching test secret from hCaptcha's docs.…