NopeCHA-compatible API

Cheaper captcha recognition. Switch by changing one URL.

Solvecha answers reCAPTCHA grids, text captchas, GeeTest sliders and FunCAPTCHA through the same API you already use. Replace the base URL. Keep the rest of your code.

  • 77.5 %of challenges on Google's reCAPTCHA demo got a token, versus 68.2 % for NopeCHA
  • 50%less than NopeCHA's monthly price for the same daily quota (about 25 % less than its 3-month billing)

Success rate measured on Google's public reCAPTCHA demo, 12 to 13 October 2026, one data-center IP (320 and 330 challenges). Results on other sites can differ.

Measured, not promised

More solved challenges

We ran our model against NopeCHA on Google's public reCAPTCHA demo. Solvecha's model got a token on more challenges.

Challenges where a token was issued Higher is better. Lines show the margin of error.
  • Solvecha
  • NopeCHA
Solvecha77.5 %
NopeCHA68.2 %

Difference +9.3 points, 95 % confidence interval +2.5 to +16.1. Test of our own model on Google's public reCAPTCHA demo. In production, requests our model cannot answer go to NopeCHA.

Show as table
Share of challenges with a token, with counts and margin of error
ProviderSuccess rateChallengesMargin of error
Solvecha77.5 %248 of 320±4.6 points
NopeCHA68.2 %225 of 330±5.0 points
What this test is, and is not

One public demo page, one data-center IP, two days in October 2026. It shows how often each model got a token there. A random-answer control got a token on 0 % of challenges. It does not show answer times, and it does not cover other sites, IPs or captcha settings. We publish a speed comparison only after an end-to-end measurement through the public API.

See prices and features side by side

Footnote: Google's public reCAPTCHA demo, one data-center IP, 12 to 13 October 2026, 320 challenges for Solvecha and 330 for NopeCHA.

Migration

Change the base URL. That is the migration.

Endpoints, request fields, response shapes and error codes follow the NopeCHA recognition API. Your polling loop, your retry logic and your SDK stay as they are.

  • Same /v1/recognition/<type> paths and the legacy root path
  • Key as key field, Bearer or Basic header, or ?key=
  • Same error codes and the same polling pattern
Migration guide
Before and after
# before
BASE = "https://api.nopecha.com"
# after
BASE = "https://api.solvecha.com"

requests.post(f"{BASE}/v1/recognition/recaptcha", json={
    "key": KEY, "task": "bus", "grid": "3x3", "image_data": [image],
})

How it works

Three calls, no SDK needed

  1. 1

    Get a key

    Create an account and copy your API key from the dashboard.

  2. 2

    Send the image

    POST the base64 image and the task text. You get a job id back at once.

  3. 3

    Poll for the answer

    GET with the id once a second. Error 14 means: not ready yet. Then the answer arrives.

Pricing

Half of NopeCHA's monthly price, plan for plan

Every plan has a daily quota of successful solves. Failed requests do not count.

Starter

$2.49/ month incl. VAT

NopeCHA: $4.99 monthly, $3.33 on 3-month billing

2,000 successful solves per day

Basic

$9.99/ month incl. VAT

NopeCHA: $19.99 monthly, $13.33 on 3-month billing

20,000 successful solves per day

Professional

$24.99/ month incl. VAT

NopeCHA: $49.99 monthly, $33.33 on 3-month billing

80,000 successful solves per day

Enterprise

$49.99/ month incl. VAT

NopeCHA: $99.99 monthly, $66.66 on 3-month billing

200,000 successful solves per day

Paid plans open soon. We e-mail you when checkout is live. Until then a new account has an API key but cannot solve captchas.

See all plan details Compare with NopeCHA, 2Captcha and CapSolver

Ready to switch?

Create an account, get your key and change the base URL. Paid plans open soon. We e-mail you when checkout is live.