Operators · run one

Run an operator.

An operator watches automations, simulates each due task and submits it inside the owner's rules. Your key stays on your machine. One command to set up, one to run.

The command

shell

npx conductor-operator init
npx conductor-operator start

init makes a new key, prints its address and waits for gas and the bond. start runs it. Use a fresh wallet that holds nothing else. Never paste a private key into a website, this one included.

How fees work

Operators are paid gas plus a small margin by the automation's owner. Each owner sets the fee on chain: gas up to a price cap, a premium and a small flat fee, capped per run and per week.
An operator is paid only when a step succeeds. If another operator lands the run first, yours reverts and you pay its gas.
New automations accept verified operators only; an owner chooses to open theirs to any operator. Fees can be zero for long stretches. This is not an investment, Conductor pays nothing on top, and no token is involved.

What you need

A machine that stays on: a small VPS, Node 24 or Docker.
A fresh key, made by init. It never leaves the machine.
A 0.01 ETH bond on Robinhood Chain, locked in the registry when you register. It is refundable: start an exit, wait 7 days, withdraw it.
A little ETH for gas on top of the bond.
An RPC endpoint. The public one works.
Outbound HTTPS for signed heartbeats. Optional; without them no uptime is shown.

Bond and exit

Registering locks 0.01 ETH in the operator registry. There is no slashing.
To leave, start an exit: the operator stops running right away and the bond unlocks after 7 days.
The registry owner can jail an operator, which only stops it from running. The bond stays yours.

Verified is granted by the registry owner to operators with 50+ runs at 98%+ success in Open mode. It can be revoked.