Runs onWrit CloudDesktopSelf-hosted
On this page
Verification step
The captcha step completes an interactive verification that occasionally appears during a legitimate flow, so a run on your own authorized account can continue. The wire format also accepts solve_captcha as an alias for the same step.
In a workflow, this is a step object with "type": "captcha". Steps run in order, and each step can read the outputs of the steps before it. See the full workflows reference for the 30+ step types.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Fields
| Field | Type | Description |
|---|
Example
A single captcha step as it appears in a workflow's steps array:
{
"type": "captcha",
"config": {}
}How it behaves
- Accepted type strings: captcha, and solve_captcha as an alias.
- Used only inside flows on your own authorized accounts and sites you have the right to access.
- Most workflows never need it; it exists for occasional friction on a legitimate path.
Where it runs
The captcha step executes wherever the run executes. On your local or BYO agent there is no compute charge and the agent can reach intranet-only systems; on Writ cloud the run is metered by running time (~$0.12 per browser-hour, from your plan’s included usage wallet.
What next
- Workflows - the full step vocabulary and the workflow object.
- Recorder - capture steps by clicking through a site.
- Managed endpoints - turn the workflow into a REST endpoint, or an MCP tool.