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 | Separate Steam/xBot proxies or a direct connection |
| 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 makes outbound connections to Steam and xBot with its API key. Steam credentials stay on your machine.
Create the worker
In the dashboard open Workers → Add worker, choose Self-hosted, and select the Steam account.
Obtain the API key
Use the regenerate-key action in the Workers list and save the key that is shown. Issuing a new key immediately revokes the previous one.
Prepare the folder
Follow the quickstart: download the Windows or Linux/macOS launcher and fill in the Steam login, password, Steam Guard secrets, and API key.
Start it
Run the local launcher and enable the worker in the dashboard. The local process must stay running and the xBot switch must stay enabled for the worker to receive jobs.
Network and proxies
A self-hosted worker opens no port and accepts no inbound connection. It needs no public IP, domain, or “worker URL”: the process calls Steam and the xBot address compiled into the release binary.
XBOT_PROXY routes all Steam traffic through a proxy; XBOT_BACKEND_PROXY covers xBot requests.
Supported schemes are http://, https://, socks5://, and socks5h://. An empty value is direct.
System proxy variables are ignored, and a failed configured proxy never falls back to direct.
Secrets and local state
Never publish a configuration containing the password, Steam Guard secrets, or API key. The Steam
session, status.json, and pending-result journal live under the user's configuration directory in
xbot-worker-go/<Steam login>. After regenerating an API key, replace it in the local configuration
before the next connection.
Managing workers
The Workers page shows each worker's type, Steam account, and enabled switch:
| Action | Available for | Effect |
|---|---|---|
| Enable / Disable | both | Allows or blocks job delivery. It does not start a self-hosted OS process. |
| Regenerate API key | self-hosted | Issues a new key and immediately revokes the previous one. |
| 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. |
The switch shows whether xBot allows the worker to operate; it does not prove that a self-hosted
process is currently running. Its actual state is available in the local log and status.json.
Refresh confirmations
The Steam Guard panel on worker and Market Bot detail pages has a refresh icon. Click it to queue a worker task requesting a fresh confirmation list. The icon stays disabled until that task finishes, not merely until the request enters the queue. Reloading the page preserves the pending lock. A successful empty response clears old confirmations; a task that finishes with an error allows another request.
The worker must be enabled and running to process the task. Network failures do not unlock the icon while the previous task's state remains unknown.