[Offcaptcha.com] captcha solving service

[mjeday]

Offcaptcha.com — another captcha solving service. You know what it's for, so straight to the point.

Flexible Pricing​

Pay-per-solve or unlimited plans with thread limits only.
Details >

Supported Captchas​

reCAPTCHA v3 | $0.15 / 1000 | from $20 / mo
Turnstile | $1.30 / 1000 | from $30 / mo
Amazon WAF | $1.30 / 1000 | from $20 / mo
PerimeterX (hsprotect) Invisible | $2.00 / 1000
PerimeterX (hsprotect) Press & Hold | $3.00 / 1000
PerimeterX Invisible + Press & Hold (plans) | from $30 / mo

Easy Integration​

API is fully compatible with anti-captcha[dot]com. Just swap the auth and domain in your request.
API Docs >

For Software Developers​

Affiliate program — 10% from every captcha solved through your software. Connect via API, details in the bot.

Get Started​

Website: offcaptcha.com
Telegram bot: @offcaptcha_bot
Telegram channel: t.me/offcaptcha

 

[mjeday]

Tasks Priority Changes​

— Tasks created under a purchased plan now have higher priority than pay-as-you-go tasks and are processed first.
— Fix: The balance now correctly displays the amount minus funds reserved for an active plan purchase. Previously, the reserved amount was not subtracted from the shown balance.

 

[mjeday]

Plan Cancellation and socks5 Proxy Support​

1. You can now cancel your purchased plan yourself directly in the Telegram bot. Funds for the unused period will be automatically refunded to your balance. The refund amount is calculated on an hourly basis.
2. Socks5 proxies are now supported. Only use this if your proxy provider doesn't offer the http protocol. There's no reason to deliberately choose a socks5 proxy — it offers no advantages.

 

[mjeday]

Browser Version Changes to FF 152​

The browser version has been updated to Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0. Please, upgrade user-agent in your http requests.

 

[mjeday]

Captcha Solving Improvements​

1. Improved humanized mouse movement behavior.

2. Servers that solve captchas now fully emulate a screen.

3. If a server becomes unavailable, tasks are now immediately stopped from being routed to it. Previously, such tasks would keep being sent to the server, and if it failed to come back online in time, they would be cancelled by timeout. Server downtime is usually caused by scheduled updates or maintenance, which led to these timeouts being exceeded.

 

[mjeday]

Created a public repository with an example of microsoft's account creation using offcaptcha.com API: link >>>

 

[mjeday]

Fixed SESSION_EXPIRED error when solving PXCaptchaPressAndHold tasks.

 

[mjeday]

Personal Account on the Website​

The website offcaptcha.com now has a personal account, which extends and simplifies the functionality of the Telegram bot. In it you can:

• top up your balance;
• manage plans (purchase, cancel, renew);
• view your payment history and purchased plans;
• get and update your API key.

To move your balance and plans over to your website account, just sign up any way you like (Google, email) and link your Telegram in the personal account.

The API key format has also changed. We strongly recommend updating it any way that's convenient — through the Telegram bot or in the website account. Old API keys will stop being supported in 30 days.

 

[mjeday]

Referral Program Improvements​

You can now get a personal referral link from your website profile or the Telegram bot to invite referrals. The default commission is 10%. Commissions are earned on captcha solves (when no softID is passed in the task creation request) and on plan purchases.

 

[mjeday]

Task and Proxy Statistics in Your Dashboard​

1. The dashboard menu now has a new Statistics section:

• Monitoring: your tasks in real time, plus the most recently solved ones.
• Tasks: a chart of solved and unsolved tasks by status and captcha type for the last 24 hours, 7 days or 30 days.
• Proxies: solve rates for each of your proxies. Group by host, ISP or country, and compare with the best result across the system.

If your PerimeterX solve rate is low, the cause is almost always your proxies. Now you can see which hosts, ISPs or countries fall behind your other proxies and the system average, and exclude them.

2. The pricing table on the website now has two new columns: success rate and solve time.

3. New API endpoints are available.

Public endpoints, no API key required:

GET /v1/statistics/system/tasks
GET /v1/statistics/system/tasks/{task_type}
GET /v1/statistics/system/proxies
GET /v1/statistics/system/proxies/{task_type}

Your account's statistics, API key required:

GET /v1/statistics/me/tasks
GET /v1/statistics/me/proxies

See the API documentation on the website for details.

 

[mjeday]

AWS waf Solver​

Added new solver for AWS waf captchas. The service supports AwsWafTask and AwsWafTaskProxyless tasks. Check the API documents. The prices and plans are available here.

 

[mjeday]

Disabling Firefox Auto-Updates​

1. In its latest release, Firefox started downloading the Widevine CDM automatically. This happened on every fresh profile used to solve a captcha, so at high solve volumes it added up to a noticeable amount of extra traffic.

Every profile now launches with updates disabled - the extra traffic is gone.

2. An issue was also found in how workers are updated: the rollout did not wait for a worker to actually come back up before moving on to the next one, which could leave part of the capacity unavailable at the same time. Workers are now updated strictly one at a time, and the next one is only taken down once the previous is fully back in service.

 

[mjeday]

Firefox updated to 158​

The browser engine has been updated from Firefox 156 to Firefox 158. Please update the User-Agent in your software:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:158.0) Gecko/20100101 Firefox/158.0

The rollout is sequential, one server at a time, and will take a few hours. While some servers still run 156 and others already run 158, PXCaptchaInvisible success rate may be lower than usual because of the User-Agent mismatch. The dip will shrink as more servers are updated and disappear by the end of the rollout.

 

[mjeday]

Microsoft signup example updated​

• User-Agent bumped to Firefox 158
• The risk/verify request now sends the msaRiskVerifySignature field instead of the deprecated msaCreateSignature, with an explicit action: SignUp
• CreateAccount now matches what the browser actually sends: empty SiteId and WReply, the redundant PrivateAccessToken removed
• Accept-Language is sent with a q-factor, just like a real browser
• Added Accept-Encoding and the Sec-Fetch-Dest / Mode / Site headers

See the latest commits.

 

[mjeday]

Service stability improved​

What was the issue​

After the upgrade to Firefox 158, browser stability issues began to occur. Workers would start to degrade after a few hours, and a restart was the only way to restore normal work.

What has changed​

The browser startup mechanism has been completely redesigned. Overall system stability has improved significantly, and workers now handle traffic spikes more reliably. Reduced infrastructure overhead has also improved solve rates, currently at 99% for PX Invisible and 81% for Press & Hold.

The new system is still being tested, so temporary performance dips may occur throughout the day.