CAPTCHA challenge solving

twocaptcha returns a solution token for a CAPTCHA that a workflow encounters. When a Beam agent hits a challenge during an approved, permitted task, it submits the challenge to the service, waits for the token, and continues the run where your rules allow. Challenges that solve cleanly pass through and the task proceeds. A challenge that fails repeatedly, returns an invalid token, or appears on a site your policy did not clear is not retried blindly. The agent stops and routes the case to a person, who decides whether the task should continue.

Token handoff and reuse

twocaptcha hands back a token meant for a single submission. A Beam agent reads the returned token, applies it to the exact request that needed it, and records the outcome where the connector allows. Successful submissions are noted and the workflow moves on. A token that arrives after the request has expired, is rejected by the target, or would be reused outside its intended scope is held. The agent notifies the owner rather than forcing it through, and a person confirms whether to request a fresh solution or halt the task.

Solve-rate reporting

twocaptcha reports whether each challenge was solved and how long it took. A Beam agent reads these results across a run, compares them to the thresholds your team set, and records the pattern where permissions allow. Steady solve rates need no action. A sudden drop in success, a spike in solve time, or a run of failures against one target is escalated. The agent notifies the owner with the counts attached, and a person decides whether to pause the workflow, change approach, or wait for the service to recover.