REACAPTCHA

verification actions for browser agents

keep browser-use
from getting stuck.

A browser task reaches a CAPTCHA and stops halfway through. rea-captcha detects it, lets the agent complete an authorized test interaction in the browser it already has, checks fresh server evidence, and continues the same task.

try the four cases →
existing browser session

browser-use task

Verification detected
✓agent action authorized
  1. detect
  2. act
  3. verify
  4. resume
DetectRead DOM, frame, URL, and runtime evidence
ActUse the agent's existing Playwright/CDP page
VerifyRequire the provider or owned server boundary
ResumeContinue only from fresh passed evidence

live provider matrix

four cases.
one agent flow.

These pages use vendor-documented non-production keys or a fully owned local boundary. They demonstrate integration behavior and provide no production anti-bot protection.

01 / GOOGLEreCAPTCHA v2

Agent checkbox action and Google Siteverify.

open case → 02 / CLOUDFLARETurnstile

Always-pass test widget and server verification.

open case → 03 / HCAPTCHAhCaptcha

Publisher test keypair and hCaptcha Siteverify.

open case → 04 / OWNEDImage / text

Authorized input and local server validation.

open case →