CAPTCHA AppID explained: how developers earn revenue share from a solver API

Peak Administrator

— 3 min read

An AppID is an identifier you attach to your API requests so a CAPTCHA solver knows the traffic came through your integration. When a solve carries your AppID, the provider pays you a cut of what that solve cost. You keep earning on solves your code triggers, including solves run by other people using your tool, with no signup link involved.

Most solver docs explain this only for their own product, and the rest of it lives buried in an SDK README. Here is the neutral version: what it is, how the money moves, how it differs from a referral link, and the one line of code that turns it on.

What is an AppID in a CAPTCHA solver?

An AppID (some services call it soft_id or a developer ID) is a short string tied to your account. You add it to the JSON body of each solve request. The provider reads it, records the solve against your ID, and credits a percentage of the cost back to you.

The point is attribution without a referral link. A referral link only pays when someone clicks it and signs up. An AppID pays on the request itself. If you ship a scraper, a browser plugin, or an SDK that calls a solver, every solve made through it can carry your AppID, whether the person running it ever heard of you or not.

How does AppID revenue share work?

The flow is simple:

  1. You create an AppID in your provider dashboard.
  2. You put it in the solve payload as a field, usually appId or soft_id.
  3. Every solve that carries the ID gets logged against your account.
  4. The provider pays you a set percentage of each of those solves.

The percentage is small per solve, because a single solve costs a fraction of a cent. It adds up through volume. A tool that runs a hundred thousand solves a month for its users is a hundred thousand chances to earn, and none of them required a conversion funnel.

They solve different problems, and plenty of developers use both.

 Referral linkAppID
Pays whenSomeone signs up through your linkA solve carries your ID
Best forBlog posts, tutorials, word of mouthTools, SDKs, bots, plugins
Needs a signupYesNo
Earns onWhat the person you referred spendsEvery solve through your integration

If you write about a solver, a referral link fits. If you build something that calls one, an AppID fits, because you earn on usage instead of on a click that may never happen.

How do I add an AppID to the API request?

On Peak it is one optional field. Create the AppID under Developer in the dashboard, then add appId to your solve payload. Here is a Turnstile solve in Python:

import requests

r = requests.post(
    "https://api.peak.fo/solve",
    headers={"X-API-Key": "pk_your_key"},
    json={
        "task_type": "TurnstileTaskProxyLess",
        "url": "https://example.com/",
        "sitekey": "0x4AAAAAAA...",
        "appId": "app_your_app_id"
    },
)

print(r.json())
# {"success": true, "data": {"token": "0.AgAAA..."}, "cost": 0.00092}

Same thing with cURL:

curl -X POST "https://api.peak.fo/solve" \
  -H "X-API-Key: pk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"task_type":"TurnstileTaskProxyLess","url":"https://example.com/","sitekey":"0x4AAAAAAA...","appId":"app_your_app_id"}'

The field is ignored when it is absent and never changes the solve result, so you can ship it in your default request and forget about it. Full details are in the earn section of the docs.

How much can you earn, and is it cash or credit?

Rates and payout form vary by provider. Some pay a flat percentage, some tier it by volume, and the reward is usually account balance rather than a bank transfer. Here is roughly where the main services sit as advertised in 2026. Tiers and terms change, so check each provider before you count on a number.

ServiceDeveloper share (AppID / soft_id)Reward form
CapSolverup to ~20%, tiered by volumeAccount balance
EzCaptcha~5% to 20%Account balance
NextCaptcha~10%Account balance
2Captcha (soft_id)~10%Account balance
Peak5% per solve, plus 20% referralSolve credit

Worth being clear about one thing, since the affiliate blogs tend to skip it: on Peak the reward is solve credit, not cash. You spend what you earn on your own Turnstile and 5s solving. That suits developers who are already buying solves. If you need a cash payout instead, a cash affiliate program is the better fit, and it is fair to say so.

When an AppID is worth setting up

If your project calls a solver and other people run it, set one up. A Scrapy middleware, a Puppeteer plugin, a Discord bot, an internal QA harness that a whole team points at the same account. Anywhere solves flow through code you wrote, the AppID turns that flow into credit without asking anyone to sign up for anything.

On Peak you can create one in under a minute. Grab an AppID under Developer, or read how the referral and AppID splits work on the earn page.

Read more