Your hardware, on the same account.

An agent is the Writ worker. Link a machine you already own with a single pairing code and it records and replays browser workflows, runs crawl shards and runs monitors — one outbound connection, no inbound ports, no public IP, happily behind NAT.

agent ▸ what it is

One worker, three jobs.

The agent is a single program you run on a machine you control. It dials out to the coordinator and waits for work; nothing dials in to it.

link ▸ two commands

Link a machine.

Two steps: mint a code in the dashboard, then run one line on the machine. You never paste a token into a shell, so nothing long-lived ever lands in your shell history.

1 · Mint a pairing code

In the app: Fleet → Connect a new agent. Over the API: POST /api/user-recorder/pair-code, which answers with the code, how long it lasts, ready-made install commands per platform, and the coordinator URL the machine should dial.

curl -X POST https://api.usewrit.app/api/user-recorder/pair-code \
  -H "Authorization: Bearer $WRIT_API_KEY"

{
  "code": "WRIT-4K2P-9XQ",
  "expires_in": 900,
  "install_commands": {
    "windows": "& ([scriptblock]::Create((irm https://api.usewrit.app/agent.ps1))) WRIT-4K2P-9XQ",
    "macos": "curl -fsSL https://api.usewrit.app/agent.sh | sh -s -- WRIT-4K2P-9XQ",
    "linux": "curl -fsSL https://api.usewrit.app/agent.sh | sh -s -- WRIT-4K2P-9XQ"
  },
  "coordinator_url": "https://api.usewrit.app"
}

2 · Run one line on the machine

Paste your own code in place of the sample. The installer fetches the agent, trades the code for its credentials, and connects:

curl -fsSL https://api.usewrit.app/agent.sh | sh -s -- WRIT-4K2P-9XQ

& ([scriptblock]::Create((irm https://api.usewrit.app/agent.ps1))) WRIT-4K2P-9XQ

Download without enrolling

Append --download-only to fetch the binary and stop — useful for imaging a machine, reviewing what you are about to run, or preparing a host that will be enrolled later. The Windows installer takes a pairing code positionally and has no equivalent flag.

curl -fsSL https://api.usewrit.app/agent.sh | sh -s -- --download-only

limits ▸ per plan

How many machines, how many doors.

Two different caps, often confused. Linked machines is how many of your own computers can be attached at once. Published endpoints and MCP tools is how many doors you can open onto them.

fleet ▸ the surface

See and manage what you linked.

Everything the Fleet page does is available over the API, under /api/user-recorder:

What the capability call tells you

One call, so a wizard can pick a target and explain a gate instead of failing with a cryptic connection error:

dispatch ▸ where work lands

Where the work actually runs.

Two paths, and they are billed differently:

uplink ▸ the shape

Uplink: a call reaching a machine with no open ports.

“Uplink” is the name for this shape, not a separate product and not an API you call. It describes what happens when someone calls a published endpoint whose workflow belongs on your machine.

1. 1 · Your agent holds an outbound connection — It dialled the coordinator; the coordinator never dials it.
2. 2 · A call arrives at your published endpoint — An ordinary HTTPS request from your own code, a partner, or an MCP client.
3. 3 · The call is handed down the connection you already have — No new socket is opened towards you.
4. 4 · The workflow runs on your machine — And the result travels back the same way.

machine ▸ what it needs

What the machine needs.

A Chromium browser driver, because the agent drives a real browser. On first browser use the agent installs it itself; you can pre-install it instead on a machine with no outbound access to the browser download, or when you would rather do it during imaging.

patchright install chromium
# or, if you already run Playwright on this machine:
playwright install chromium

reference ▸ next

Keep going

faq

Fleet questions, answered.

end ▸ connect

Link the first machine.

Mint a code, run one line, and the machine is part of your fleet before the code expires.