CapSolver

A wrapper around the CapSolver API

If there's problems with this service, you can contact official support through 2captcha's Official Site or try DeathByCaptcha's API

Features

• Promise Based API methods
• Browser & NodeJS support
• Node-Fetch EMCAScript
• Fluent typings & native TS.
• Proxy Support

Currently Supports:

• Google Recaptcha (v2/v3/enterprise),
• hcaptcha,
• FunCaptcha,
• base64 image captchas

Planned Coverage

• Funcaptcha
• DatadomeSlider
• AntiKasada
• AntiAkamiBMP

Install

npm install capsolver

yarn add capsolver

Usage

Recaptcha,

import CapSolver from "capsolver"

// A new 'solver' instance with our API key
const solver = new CapSolver.Solver("<Your captchaai api key>")

/* Example ReCaptcha Website */
// solver.<recaptchaV2 | recaptchaV2Enterprise | recaptchaV3>
solver.recaptchaV2("6Ld2sf4SAAAAAKSgzs0Q13IZhY02Pyo31S2jgOB5", "https://patrickhlauke.github.io/recaptcha/")

.then((res) => {
    console.log(res)
})
.catch((err) => {
    console.error("Could not solve captcha.")
})

Image,

import CapSolver from "capsolver"
import fs from "fs";

const solver = new CapSolver.Solver("<Your captchaai api key>")

// Read from a file as base64 text
solver.imageCaptcha(fs.readFileSync("./captcha.png", "base64"))
.then((res) => {
    console.log(res)
})
.catch((err) => {
    console.error("Could not solve captcha..")
})

Proxy,

import CapSolver from "capsolver"

const solver = new CapSolver.Solver("<Your captchaai api key>")


solver.recaptchaV2("6Ld2sf4SAAAAAKSgzs0Q13IZhY02Pyo31S2jgOB5", "https://patrickhlauke.github.io/recaptcha/", {
    proxyAddress: "login:password@21.214.43.26", // The (Username : Password @ Address) of our chosen proxy
    proxyType: "HTTP" // The 'Type' of proxy, http, https, socks, ect.
    proxyPort: 8080
})

.then((res) => {
    console.log(res)
})
.catch((err) => {
    console.error("Could not solve captcha..")
})

Commit Guidelines

The latest version of the code base will always be under the 'next' branch!

• All pull requiests must provide a valid reason for the change or implementation
• All CORE CHANGES require an issue with reasoning made before a PR will even be addressed.
• All PR's must follow the general structure of the code base
• If you have questions, feel free to make an issue and i'll get to it right away!

---