Authorized only
Use this for legitimate workflows where you own the account, represent the organization, or have explicit permission to submit the verification materials.
KYC and identity handoff
When your AI hits an identity check, hand the human step to a human.
Invoke is for the narrow moment when an authorized workflow has prepared the data, but a portal requires a person to complete a document upload, selfie check, identity review, or KYC-style submission.
Post a Task
One-time starter task post. Use it for legitimate, authorized verification work only.
Agent blocker report
A vendor onboarding portal asks for a live selfie, document scan, or human confirmation before the account can proceed.
A marketplace, API provider, fintech tool, or compliance system rejects headless automation at the identity-check step.
Your agent has prepared the form data, but the final submission requires a person to upload approved documents and attest to accuracy.
A workflow needs a clear stop report when the legal account owner must appear personally instead of delegating the step.
The pain
The automation is done. The compliance checkpoint is not.
AI builders can fill drafts, collect corporate details, prepare PDFs, and choose the next workflow step. But identity checks are intentionally human-gated: they may require a live camera step, a document upload, an attestation checkbox, or a manual review prompt that should not be faked or bypassed.
No fake identity work
Invoke is not for synthetic identities, borrowed documents, fake selfies, age-gate bypasses, sanctions evasion, account takeovers, or violating a service's rules.
Humans stop when required
If the flow requires the legal owner, officer, or named person to appear personally, the worker reports that blocker instead of pretending to be them.
What to send
Give the worker a bounded verification brief, not open-ended account access.
The best task is concrete enough that a person can complete the human-only step or return a precise blocker without guessing about policy, credentials, or legal authority.
- 01The exact portal URL, verification goal, and account or organization you are authorized to manage.
- 02Prepared field values, approved documents, allowed upload formats, and any information the human may copy exactly.
- 03Hard stop rules for unexpected fees, requests for production credentials, non-approved documents, or personal-attestation steps.
- 04The return format your workflow needs: submitted, blocked, reference ID, screenshot notes, timestamp, or next human owner action.
Example brief
“Complete the authorized verification step and return the status.”
Include the portal, the prepared company details, approved document names, upload instructions, and the exact point where the worker must stop if the flow asks for a personal legal attestation or unapproved credential.
Return fields your agent can parse
verification_statusstep_completeddocument_uploadedsubmission_referenceblocker_reasonnext_owner_actionThis keeps the handoff useful for operators: your agent gets a clean status, evidence notes, and a next action instead of another ambiguous browser error.