Skip to content

Feature Request πŸš€ β€” Optional 10Captcha Integration for CAPTCHA SolvingΒ #41

Open

Description

@TomX99

Hi @hyperbrowserai team,

Thank you for the great work on HyperAgent β€” it's an impressive project for AI-powered browser automation.

I’d like to suggest adding optional support for 10Captcha, a simple and affordable CAPTCHA-solving API. Many users working with browser automation face CAPTCHA challenges, and having a built-in option to solve them would make HyperAgent even more reliable and user-friendly for real-world automation tasks.

The API is easy to integrate and well-documented: https://10captcha.com/api-docs.php

I believe this would be a valuable addition for users dealing with protected websites.

Thanks for considering this!

Activity

  1. Shraman123 commented on Aug 26, 2026

    @Shraman123

    I put together an implementation of this (10Captcha integration) as a solveCaptcha agent action:

    Branch: https://github.com/Shraman123/HyperAgent/tree/feature/10captcha-integration
    Diff: main...Shraman123:HyperAgent:feature/10captcha-integration

    Summary:

    • src/agent/captcha/ten-captcha-client.ts β€” client for 10Captcha's in.php/res.php submit-and-poll API (image CAPTCHAs + reCAPTCHA v2), with per-type timeouts and defensive response parsing.
    • src/agent/actions/solve-captcha.ts β€” the solveCaptcha action: screenshots + solves + optionally fills image CAPTCHAs, or solves + injects the token for reCAPTCHA v2.
    • Registered in DEFAULT_ACTIONS only when TENCAPTCHA_API_KEY is set (same pattern as GEMINI_API_KEY β†’ PDFActionDefinition), so it's fully opt-in with zero behavior change otherwise.
    • README section documenting the new env var and action.

    tsc, eslint, and yarn build (run directly via tsc/tsc-alias) all pass clean on this branch. I also exercised the client against a mocked fetch covering the happy path, CAPCHA_NOT_READY polling, submission/poll errors, timeouts, and reCAPTCHA v2 request params.

    I can't open a PR directly β€” looks like this repo restricts PR creation to collaborators (same thing @RagavRida ran into on #90). Happy to have a maintainer open the PR from the branch above, or add me as a collaborator so I can open it myself. Let me know if you'd like anything changed first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions