Human checkpoint tasks

Your AI filled the form. A human needs to finish the signup.

Use Invoke when an automation run reaches a legitimate website signup, intake form, or account creation step that stops at CAPTCHA, phone verification, or anti-bot friction. Set a reward amount ($10–$500) for a person to complete the authorized step and report back exactly what happened. We take 10% (min $1) as platform fee, and the human earns the rest.

Post a Task

One authorized website step · no subscription · use the live Invoke Starter checkout.

Demo output

handoff result

{
  "task_status": "submitted",
  "site_step_completed": "demo intake form",
  "verification_method": "phone code entered by human",
  "confirmation_note": "confirmation screen reached",
  "submission_reference": "shown on page",
  "remaining_blocker": null
}

Demo framing only. Send the exact return fields your workflow needs.

Exact failure mode

The browser agent did the easy part. The site wants a person.

This page is for small, concrete handoffs where the automation plan is ready and the remaining work is a human-only checkpoint.

CAPTCHA checkpoint

The page loads, your browser agent fills the fields, and the final button is gated by a challenge intended for a person.

Phone or SMS verification

The form requires a one-time code, a quick call, or a real-time confirmation step before the account can be created.

Anti-bot form friction

The site slows down headless browsers, rejects repeated attempts, or asks for subjective intake details before submission.

What to send

Give the human the prepared path, not a vague errand.

The best request is narrow: finish this account setup or form submission, stop under these conditions, and return these fields.

The website URL and the exact account, signup, or intake goal.

Field values your agent already prepared, plus any fields the human may answer from context.

Rules for stopping: paid upgrades, sensitive data, unsupported countries, or unexpected questions.

The return format you need: login status, submission ID, screenshot notes, or blocker details.

Suggested return fields

Make the result machine-readable after the human step.

task_status

site_step_completed

verification_method

confirmation_note

submission_reference

remaining_blocker

Boundaries

Use this for legitimate, authorized workflows.

This is for forms and accounts you are allowed to create or submit. Do not use it for spam, deception, ban evasion, fake identities, or accessing systems you are not authorized to use.

Good fit: “Create the vendor portal account with these company details, stop if it asks for payment, and return the confirmation screen text.”

Buyer FAQ

Security and handoff boundaries before you buy.

Keep the task narrow, authorized, and safe for a human to complete.

What signup help can Invoke assist with?

One authorized website signup, account-creation step, intake form, or submission checkpoint where your agent already knows the goal and needs a person to finish the human-only step.

What should I send with the task?

Send the URL, prepared field values, business details you are authorized to use, stopping rules, and the return format you need. If a new password is required, use a unique temporary value for that new account only.

What should I not send?

Do not send production passwords, private keys, seed phrases, broad admin credentials, payment card numbers, 2FA backup codes, or access to accounts unrelated to the signup task.

Can humans handle CAPTCHA, phone verification, or anti-bot friction?

Yes, within authorized boundaries: a person can complete legitimate human checkpoints, enter a one-time code you provide, or report what blocked the flow. Invoke is not for ban evasion, spam, fake identities, scraping protections, or violating a site’s terms.

What happens after I set a reward and pay the platform fee?

Checkout creates one starter task. You provide the handoff details, the human works only inside those instructions, stops on sensitive or unexpected steps, and returns the status, confirmation notes, references, or remaining blocker.

Set the reward for one bounded signup handoff; use the task details to define the exact authorized step and stop conditions. Invoke takes 10% (min $1) as platform fee.Related: human identity verification and KYC handoffs for AI agents →Related: human phone OTP receipt and verification-code handoffs →Related: human inbox monitoring and email reply handling for AI agents →