NopeCHA no longer solves hCaptcha.
NopeCHA discontinued hCaptcha on October 2, 2026. Their API now refuses hCaptcha calls, and users report the extension has stopped solving them. NoneCap is an hCaptcha solver with an API, a Chrome extension and monthly plans.
What NopeCHA said
Users opened bug reports on NopeCHA’s GitHub when hCaptcha solving stopped with the error “This API endpoint has been discontinued”. A NopeCHA collaborator answered:
“This is working as intended, the hCaptcha API endpoint has been discontinued and support will be removed in a future extension release.”
Source: NopeCHA’s extension repository on GitHub, October 2, 2026. NopeCHA’s API reference has since dropped the hCaptcha token endpoint and lists a new error, “Endpoint Discontinued” (HTTP 410, code 19).
What to do now
If you called the NopeCHA API
Follow the switch guide. It maps every field of NopeCHA’s
hCaptcha token request (sitekey, url, data.rqdata,
proxy) to its NoneCap name, lines up the error codes, and has working
snippets for curl and the official Node
and Python SDKs.
New accounts get 1,300 free credits, so you can test against your
own sitekeys before paying anything. Sign up through this link and your first top-up
also gets +25% extra credits.
If you used the NopeCHA extension
Install the NoneCap Chrome extension from the Chrome Web Store. It solves hCaptcha while you browse, gives you 100 free solves a day with no account, and can be paused on any site. If you need more than that, add a NoneCap API key in its options. What it captures is on the extension privacy page.
NoneCap vs NopeCHA at a glance
| NoneCap | NopeCHA | |
|---|---|---|
| hCaptcha | Supported: regular, invisible, enterprise rqdata | Discontinued October 2, 2026; the endpoint answers HTTP 410, code 19 |
| Other captchas | None; hCaptcha only | reCAPTCHA v2/v3 and Turnstile tokens, plus image recognition for several other types |
| Browser extension for hCaptcha | Chrome extension, 100 free solves a day, no account | hCaptcha support “will be removed in a future extension release” |
| Billing model | Prepaid credits, or a monthly plan with a set number of solves a day | Monthly or quarterly subscription |
| Credit expiry | Never expire | Credits refill every 23 hours |
| Daily cap | None on credits. Plans give 400 to 8,000 solves a day, then you carry on with credits | Fixed credits per day per plan (2,000 to 200,000) |
| Failed solves | Never charged | Not stated on the pricing page |
| API | REST submit and poll with Bearer auth; Node and Python SDKs | REST API, Python and Node.js clients |
| Free tier | 1,300 credits on signup | Not listed on the pricing page |
NopeCHA’s plan details come from its pricing page and API reference.
How NoneCap bills
NopeCHA sells a subscription: $4.99 to $99.99 a month for 2,000 to 200,000 credits a day, refilling every 23 hours. NoneCap has a plan too. Plans run from $4.99 a month for 400 hCaptcha solves a day up to $99.99 for 8,000, and paying every 3 months saves about 17%. When the day's solves are used up, you keep solving on credits.
Or skip the plan and pay as you go: you top up prepaid credits, spend from 1 credit per hCaptcha challenge round (hCaptcha decides how many rounds, often one and sometimes two or three), and the credits never expire. Credits have no monthly fee and no daily ceiling. Credits come off the balance only when a solve returns a token, so a failed solve costs nothing. Packs run $0.20 to $0.50 per 1,000 credits; the pricing page has the details.
The NoneCap call
Both services hand back a real hCaptcha token, so the code that submits
h-captcha-response stays as it is. Only the solver call changes: send
POST /v1/solves, optionally wait for the result with
?wait=N, and read the token field.
curl "https://api.nonecap.com/v1/solves?wait=90" \
-H "Authorization: Bearer $NONECAP_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "hcaptcha",
"sitekey": "f5ab1c2d-7e8f-4a9b-b1c2-d3e4f5a6b7c8",
"url": "https://target.example/login"
}' {
"id": "solve_01HQF7K3JKWZX",
"object": "solve",
"type": "hcaptcha",
"status": "solved",
"token": "P1_eyJ0eXAi...UV8w",
"credits_charged": 1
}
A 202 means the solve was still running when the wait ended; poll
GET /v1/solves/{id} until it finishes. The
switch guide has the full mapping and the
API reference documents every field.
Enterprise hCaptcha (rqdata)
NopeCHA took enterprise rqdata under data.rqdata. On NoneCap
send type: "hcaptcha_enterprise" and put rqdata at the top
level of the body, fresh for each challenge, when the site provides one. NoneCap
returns tokens that enterprise sitekeys accept.
When NopeCHA is still the better fit
NoneCap solves hCaptcha and nothing else. If you also need reCAPTCHA v2/v3 or Cloudflare Turnstile, NopeCHA’s API reference still lists both, and NoneCap does not solve them. You can keep NopeCHA for those and move only your hCaptcha traffic.
Last updated October 2026.
Frequently asked
Did NopeCHA discontinue hCaptcha?
Why is NopeCHA hCaptcha not working?
Can I point a NopeCHA client at NoneCap?
/v1 and does not implement NopeCHA’s wire protocol, so the solver call needs rewriting. The switch guide has the field-by-field map and snippets for curl, Node and Python.