CapMonster Alternative for Cloudflare Turnstile: SolveGate Compared

Start with the limitation

SolveGate covers two things: Cloudflare Turnstile widgets and the Turnstile-powered challenge pages Cloudflare serves in front of a site. Cloudflare documents three widget modes — managed, non-interactive and invisible — and SolveGate handles all three through the same call. It does not solve reCAPTCHA, hCaptcha, GeeTest, FunCaptcha or AWS WAF. CapMonster Cloud prices every one of those categories on its public pricing table.

• CapMonster Cloud publishes rates for reCAPTCHA v2 and v3, both Enterprise variants, Cloudflare Turnstile, Cloudflare Bot Challenge, Amazon WAF, Tencent, GeeTest, Yidun and text captcha. Its client libraries additionally expose request types for DataDome, Imperva, FunCaptcha, MTCaptcha, Prosopo, Altcha and others.
• SolveGate exposes one endpoint with two gate values: turnstile and waf.
• A mixed queue — Turnstile on one target, reCAPTCHA on another — cannot run on SolveGate alone.

That is the whole trade. The rest of this page is for the case where Turnstile is most or all of your volume, and for deciding honestly whether that is true of you.

Documented differences, side by side

Every CapMonster Cloud figure below comes from its public pricing table and FAQ, or from the registry metadata of its official client packages. Nothing here is inferred from behaviour or from third-party write-ups.

One gap worth naming: CapMonster Cloud's API reference at docs.capmonster.cloud returned HTTP 403 to automated retrieval on the day this page was checked, so no endpoint names, parameter names or error codes are quoted from it here. Open it in a browser before you write integration code. The task-type names above come from the READMEs of its own published npm and PyPI clients, which are retrievable.

CapMonster Cloud prints a success-rate figure beside each type in its pricing table, including 99% for Turnstile. That is its own published measurement, reproduced here as a documented attribute rather than as an independent result. This page makes no measured reliability claim about either service.

What Turnstile volume costs on each

CapMonster Cloud's Turnstile rate is flat at $1.30 per 1,000 tokens. SolveGate is not metered pay-as-you-go: you buy a prepaid pack of credits, one credit is one successful solve, and the size of the pack sets the effective rate. Credits do not expire. This is the full catalogue.

The comparison below anchors each volume on the pack that covers it, rather than multiplying out a per-1,000 rate.

At 10,000 solves the gap is narrow — $12 against $13, roughly 8 percent — and two thirds of the pack sits unused until later runs, though it does not expire. At 100,000 it is $25 against $130, roughly 81 percent lower. At 1,000,000 it is $150 against $1,300, roughly 88 percent lower.

Two adjustments to make before you treat that as the whole picture. CapMonster Cloud's bonus program credits 5% back to your balance once you have solved $500 worth, 10% at $1,000 and 15% at $10,000, which lowers its effective rate at sustained volume. It also documents a refund within three days of purchase if the service does not suit you, which SolveGate does not describe on this page. And SolveGate's rate is fixed by the pack you buy rather than by the volume you end up using: on the 30,000 pack every solve costs $0.40 per 1,000 whether you spend 5,000 credits or all 30,000.

When CapMonster Cloud is the better choice

Breadth is a real advantage and it is theirs. Pick CapMonster Cloud when any of the following is true.

• Your targets present more than one captcha family. One account, one balance and one client library covering reCAPTCHA, GeeTest, Amazon WAF, Tencent, DataDome and Imperva is worth more than a lower unit price on the Turnstile slice.
• You need reCAPTCHA v2 in bulk. Its published $0.04 per 1,000 images, marked as proxy-included, is far below what a Turnstile-only service can offer you, because a Turnstile-only service offers it at all.
• Your stack is C#, Go or PHP. CapMonster Cloud lists official SDKs for five languages; SolveGate publishes two, for Node and Python.
• You want a browser extension for interactive work. CapMonster Cloud ships Chrome and Firefox extensions alongside the API.
• You need a contractual SLA and a named account manager. Its business page publishes a 99.9% SLA; SolveGate does not offer an equivalent.
• You are already on ZennoPoster, where the 5,000 free test captchas and existing integration apply.
• Your Turnstile volume is a few thousand solves a month. The smallest SolveGate pack is 30,000 credits for $12, so a very small run pays for capacity it will take a while to use.

If two or more of those describe you, stop here. Splitting a small Turnstile volume across a second vendor is not worth the extra key, invoice and failure mode.

When SolveGate is the better fit

• Turnstile is effectively all of your captcha volume, and the published difference is one you will feel: $1.30 per 1,000 on CapMonster Cloud against $0.40 per 1,000 on SolveGate's 30,000-credit pack, or $0.25 per 1,000 once you buy the 100,000 pack.
• You need Turnstile-powered WAF challenge pages and Turnstile widgets handled by the same call, with one gate parameter switching between them.
• You want to try it without contacting anyone: the first 1,000 solves are free, rather than a test balance granted on request.
• You want a sandbox key that cannot be confused with a live one. A sk_test_ key returns "mode": "sandbox" on every response and never clears a real gate, so a misconfigured CI job fails loudly instead of shipping a worthless token.
• Your runtime is Node 18+ or Python 3.9+.

SolveGate returns a token in typically under 1.5 seconds. That is its own published figure, in the same category as the numbers CapMonster Cloud prints; neither is independently measured here.

Calling SolveGate for a Turnstile token

One POST, bearer-authenticated. Synchronous by default — the request blocks until the gate clears or times out. Set async: true to get a pending solve back immediately and poll GET /v1/solve/{id}, which is free.

curl -s https://api.solvegate.io/v1/solve \
  -H "Authorization: Bearer $SOLVEGATE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "gate": "turnstile",
    "sitekey": "0x4AAAAAAAAA_target",
    "url": "https://staging.example.com/login"
  }'

# For a Cloudflare challenge page in front of the site, send "gate": "waf".

The response carries status (pending, solved or failed), token, solve_ms, mode and billed. Check mode before you trust a token: a sandbox value means a test key produced it. On failure you get error_code and error_message instead, and billed is false.

import json, os, urllib.request

KEY = os.environ["SOLVEGATE_KEY"]

def solve(gate, sitekey, url):
    body = json.dumps({"gate": gate, "sitekey": sitekey, "url": url}).encode()
    req = urllib.request.Request(
        "https://api.solvegate.io/v1/solve",
        data=body,
        headers={
            "Authorization": f"Bearer {KEY}",
            "Content-Type": "application/json",
        },
    )
    with urllib.request.urlopen(req) as r:
        return json.load(r)

s = solve("turnstile", "0x4AAAAAAAAA_target", "https://staging.example.com/login")

if s["status"] != "solved":
    raise RuntimeError(f'{s["error_code"]}: {s["error_message"]}')
if s["mode"] != "live":
    raise RuntimeError("sandbox token: use an sk_live_ key for real targets")

print(s["token"], s["solve_ms"], "billed:", s["billed"])

Whichever service you use, the token has the same shelf life. Cloudflare documents the Turnstile validation token as valid for five minutes, single-use, with a replayed token rejected by siteverify as timeout-or-duplicate. Submit it promptly and do not cache it across runs.

Running both

These are not mutually exclusive. A common arrangement for a mixed queue is to route by challenge type at the call site.

• Send Turnstile and Cloudflare challenge pages to SolveGate, where a credit pack costs less per solve than $1.30 per 1,000.
• Send reCAPTCHA, GeeTest, Amazon WAF, DataDome and the rest to CapMonster Cloud, which prices them.
• Keep one wrapper function per challenge type so the routing decision lives in one file and can be reversed in one commit.
• Watch the balance on both. Two prepaid balances means two ways to run dry mid-run.

If the Turnstile share of your volume is small, this split is overhead for little return. Measure the share first.

What you point this at

SolveGate is built for automation against properties you own or are authorised to test: QA suites, CI pipelines, uptime monitoring, staging environments and verifying that your own anti-bot configuration behaves as intended. Clearing challenges on someone else's site without permission is your problem to answer for, not a capability either vendor's pricing table changes.

Common questions

Related

More in Alternatives