A NopeCHA alternative built only for hCaptcha.

NoneCap is a hosted, pay-per-solve hCaptcha API. Like NopeCHA it returns a real token your client submits as a normal h-captcha-response. The difference is the billing: instead of a monthly subscription with a daily credit cap, you buy prepaid credits that never expire and pay only for the solves you use.

NoneCap vs NopeCHA at a glance

The core difference is the billing model

NopeCHA is a subscription. You pick a plan ($4.99 to $99.99/month) and get a fixed number of solves per day, from 2,000 on Starter up to 200,000 on Enterprise, and that quota refills every 23 hours. Whatever you don’t use that day is gone, and you can’t exceed the daily cap when a job spikes.

NoneCap is pay-as-you-go. You top up prepaid credits, spend 1 credit per hCaptcha challenge round (hCaptcha decides how many, often one and sometimes two or three), and the credits never expire. There’s no monthly fee and no daily ceiling to bump into when load spikes. Failed solves are refunded automatically, so a bad run costs you nothing.

Pricing, honestly

Which is cheaper depends entirely on your usage pattern, so here are the real numbers rather than a blanket claim:

• Steady, high daily volume that fully uses a plan’s daily cap: NopeCHA’s subscription can be the cheaper per-solve option.
• Variable, bursty, low, or unpredictable volume: NoneCap is usually cheaper. You pay only for what you solve ($0.25 to $0.50 per 1,000 credits), there’s no unused quota to waste, and a slow week costs you nothing.

There’s no recurring bill and no “use it or lose it” quota, and failures get refunded. For scrapers and automation rigs whose load isn’t flat, that makes the spend a lot easier to predict.

Same token, easy migration

Both services hand back a real hCaptcha token, so migrating is mostly a base-URL and key change. Create a solve, optionally block 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 '{
    "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
}

Dropped into a Python helper, the whole flow is a few lines:

import os, requests

NONECAP_KEY = os.environ["NONECAP_KEY"]

def solve_hcaptcha(sitekey: str, url: str) -> str:
    r = requests.post(
        "https://api.nonecap.com/v1/solves",
        headers={"Authorization": f"Bearer {NONECAP_KEY}"},
        params={"wait": 90},               # block up to 90s for the token
        json={"sitekey": sitekey, "url": url},
        timeout=120,
    )
    r.raise_for_status()
    return r.json()["token"]                # a real P1_… hCaptcha token

# Submit the returned token as the form's h-captcha-response field.

For long-running jobs you can skip ?wait and pass a webhook_url instead, or poll GET /v1/solves/{id}. See the API reference for the full object and every language example.

Enterprise hCaptcha (rqdata)

Enterprise hCaptcha binds each challenge to a fresh rqdata blob, which is where pure image-recognition solvers tend to struggle. NoneCap returns tokens that enterprise sitekeys accept. If enterprise rqdata is why you’re shopping for an alternative, this is the strongest reason to pick NoneCap: a token enterprise accepts, minted on demand.

When NopeCHA is the better fit

Be honest with yourself about scope. If you need to solve reCAPTCHA v2/v3, Cloudflare Turnstile, or FunCaptcha, NopeCHA covers them and NoneCap does not yet (those are on the roadmap). And if your hCaptcha volume is high and perfectly steady, a maxed-out NopeCHA daily plan can beat pay-per-solve on raw price. NoneCap wins when you want hCaptcha depth with credits that never expire, refunds on failures, and no subscription.