Worker
The process that talks to Steam — cloud or self-hosted, how to get one, and how to keep it running.
A worker is the process signed into a Steam account. Every action a Market Bot decides on — placing a buy order, listing an item, cancelling, reading price history — is executed by the worker.
No worker, no trading
A Market Bot is only the decision layer. Without a running worker attached to the same Steam account its jobs pile up in the queue and nothing reaches Steam.
One Steam account can have exactly one worker.
Cloud or self-hosted
| Cloud | Self-hosted | |
|---|---|---|
| Where it runs | On XBOT infrastructure | On your own machine or server |
| Proxy | Dedicated proxy, hosted by us | Yours — whatever the machine uses |
| Steam credentials | Stored in XBOT: password, shared_secret, identity_secret | Stay on your machine |
| Setup | Create it and it runs | Download the build, connect it with an API key |
| Billing | Per tariff, shown before creation | Not billed as a cloud worker |
Cloud worker
We host the worker together with its proxy — nothing has to be installed on your side. When creating one you provide:
- The Steam account.
- A proxy — buy a new dedicated one (choose a location) or attach a proxy you already own.
- Steam credentials: password,
shared_secretandidentity_secret. The two secrets can be imported from a.maFileinstead of being typed in.
Credentials and proxy stay editable afterwards from the worker list.
Self-hosted worker
The worker runs on your hardware and connects to XBOT over its API key. Steam credentials never leave your machine.
Create the worker
In the dashboard open Workers → Add worker, choose Self-hosted and the Steam account.
Download the build
Grab the latest version from dl.xbot.gg. The same link sits on the Workers page (Download worker) and inside the create-worker dialog.
Connect it
Open the worker page, copy the API key and put it into the worker configuration. Set the worker URL so the dashboard can reach it. The key can be regenerated from the worker list at any time — the worker stops being accepted until it gets the new one.
Start it
Start the worker and switch it on in the dashboard. The row turns Running and starts reporting uptime and ping.
Managing workers
The Workers page lists every worker with its type, status, Steam account and uptime:
| Action | Available for | Effect |
|---|---|---|
| Start / Stop | both | Switches the worker on or off. A stopped worker stops taking jobs. |
| Regenerate API key | self-hosted | Issues a new key; the old one stops working immediately. |
| Edit credentials | cloud | Updates the Steam password and Steam Guard secrets we store. |
| Change proxy | cloud | Moves the worker to another proxy. |
| Delete | both | Removes the worker. The Steam account stays, and can get a new worker. |
Status values: Running — connected and taking jobs; Idle — switched off; Error — the worker is failing to work with Steam.