Add CaptchaAI as a provider option?

[bshahin101]

Hi — solid library. Since it already integrates 2Captcha for solving, adding CaptchaAI as a provider option is a thin addition (2Captcha-compatible API, same call shape). Happy to send a PR adding it if you'd welcome it — covers Turnstile, reCAPTCHA v2/v3, Cloudflare Challenge, GeeTest. No pressure.

[bshahin]

Following up on this — and starting with a correction to my own issue above.

Correction: I listed GeeTest in the original description. That's wrong, and I'd rather fix it than leave it standing. CaptchaAI solves reCAPTCHA v2 / v3 / Enterprise, Cloudflare Turnstile, and image captchas — it does not solve GeeTest (or hCaptcha / FunCaptcha). Apologies for the sloppy scope.

The more useful part: I filed this as a feature request without realising CaptchaAI was already integrated here — and looks to have been removed by accident.

• Added in 1c4137f3 "Add CaptchaAI" (2025-07-14), as your own response to Suggestion: Add CaptchaAI API as optional CAPTCHA solver #2 — 13 files: SolverType.captchaai, a vendored async client, reCAPTCHA v2 + v3 solvers, two examples, an integration test, plus README and .env.example entries.
• Removed in 7dc6299f "Fix open closed shadow root inside iframe" (2026-04-03). That commit deletes all 13 CaptchaAI files, the captchaai enum member, the .env.example key and the README section — while leaving twocaptcha and tencaptcha untouched. Given the commit's subject is a shadow-DOM fix, this reads like a stale-base clobber rather than an intentional removal.

Two things that corroborate it:

1. The example you linked when you closed Suggestion: Add CaptchaAI API as optional CAPTCHA solver #2 — examples/recaptcha/captchaai_v2.py — now 404s.
2. At main, playwright_captcha/types/solvers.py has twocaptcha and tencaptcha but no captchaai.

While looking at that commit I also noticed TenCaptchaSolver isn't exported from playwright_captcha/__init__.py (only TwoCaptchaSolver is) — possibly collateral from the same change, worth a glance independently of this.

Offer: happy to send a PR restoring the provider rebased onto current main, mirroring the existing tencaptcha package structure exactly. Strictly additive and opt-in — no behaviour change unless a CAPTCHA_AI_API_KEY is set, nothing existing touched. Scope would be reCAPTCHA v2 + v3 (what was there before); Turnstile could follow separately since that needs a small turnstile() wrapper on the client rather than a straight restore.

Want me to open it? Happy to leave it alone if the removal was deliberate.

(Posting from my main account — same person as @bshahin101 who opened the issue.)