agent setup guide
Get a machine earning in ten minutes.
On Windows it is one download and a double-click — the starter asks for your key and remembers it. On macOS and Linux it is one Node file and two environment variables. Either way you keep using the slicer you already print with.
1 · Register the machine and keep its key
Registering issues the API key the agent signs in with. It is shown once, so paste it straight into the command below.
2 · Start the agent with your key
Node 20 or newer, no dependencies. Windows needs one file: the starter checks for Node and installs it when it is missing or too old, fetches the agent, then asks for the key and your commands once and remembers them. After that it runs in the notification area — nothing has to stay open.
- 1 · Keep start-maker-agent.bat in its own folder, for example Downloads\maker-agent.
- 2 · Double-click it. If Windows warns, choose More info, then Run anyway. If Node.js is missing it installs the LTS build first — approve the Windows prompt when it appears.
- 3 · Sign in before downloading and there is no key to paste — the file carries one bound to your account. Signed out, it asks for the key from step 1.
- 4 · Paste your slicing command when it asks — or press Enter to skip and take work without slicing.
- 5 · Nothing to type for generation: the built-in OpenMesh runner is fetched with the agent, and the pipelines it drives are installed for you — the fast model, the high-detail Hunyuan3D-2 in its own environment, and Blender for surface finishing. That download is large and happens once.
- 6 · That window closes and an orange 3 appears in your notification area. The icon shows what the machine is doing right now: an open grey ring while it checks in with the site, orange while it waits for work, and green with a running clock while it processes a model. Right-click it to open the log, restart it or stop it.
- 7 · It also puts a shortcut in your Windows startup folder, so the machine rejoins the network every time you log in. Untick Start with Windows in the same tray menu to turn that off.
if double-click does nothing, run it from PowerShell
cd $HOME\Downloads .\start-maker-agent.bat
example slicing command
"C:\Program Files\Prusa3D\PrusaSlicer\prusa-slicer-console.exe" --export-gcode --output {file} {input}The network hands the mesh over as {input} and expects the result at {file}. Whatever your tool writes there is uploaded back with the job.
3 · pick your slicer
PrusaSlicer on macOS, Windows or Linux
The console build ships inside the PrusaSlicer app bundle. Point --output at {file} and the agent uploads the gcode it writes.
MP_TASK_COMMAND="prusa-slicer --export-gcode --output {file} {input}"- ·macOS: /Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer
- ·Windows: "C:\Program Files\Prusa3D\PrusaSlicer\prusa-slicer-console.exe"
- ·Add --load your-profile.ini to slice with your own settings and material.
4 · Optional: take generation jobs (self-hosted engines)
A GPU machine running open weights can answer TripoSR, TRELLIS and Hunyuan3D. The network routes a job to the command for that engine and passes MP_ENGINE, MP_WEIGHTS and MP_OUT; your pipeline writes a .glb, .gltf, .stl, .obj or .ply to MP_OUT. Set the engines your machine runs when you register it, so routing only sends it work it can finish.
The starter already installs the built-in runner as the generation command, so a GPU machine takes models with nothing typed. It runs whichever pipeline it finds and, when none is installed, names the one it is missing. Point it at your own with MP_TRELLIS_SCRIPT (or MP_TRIPOSR_SCRIPT / MP_HUNYUAN3D_SCRIPT), or use one command for every engine:
MP_GENERATE_COMMAND_TRELLIS="python trellis_run.py" \ MP_GENERATE_COMMAND_TRIPOSR="python triposr_run.py" \ MP_GENERATE_COMMAND_HUNYUAN3D="python hunyuan3d_run.py" \ node maker-agent.mjs
An engine without its own variable falls back to MP_GENERATE_COMMAND:
MP_GENERATE_COMMAND="python run_weights.py" # used for any engine without its own variable
- MP_IMAGE · reference image or concept frame to reconstruct
- MP_PROMPT · the prompt the maker typed
- MP_ENGINE · engine id the job asked for
- MP_WEIGHTS · the open-weights repo this job was routed to, e.g. microsoft/TRELLIS
- MP_TOPOLOGY · triangle or quad
- MP_POLYCOUNT · target polygon count
- MP_OUT · path your pipeline must write the mesh to
High detail: Hunyuan3D-2
The open-weight model in the same class as Meshy and Tripo: it generates the object itself instead of guessing one depth field, so faces, hands and hard edges survive. It runs in its own Python 3.10 environment beside TripoSR, and a model can take many minutes — that is the trade for the detail.
Download the high-detail installer- 1 · Save install-hunyuan3d.bat in the same folder as start-maker-agent.bat.
- 2 · Double-click it. It installs Python 3.10 and PyTorch, then the model — around 10 GB the first time.
- 3 · When it says Done, right-click the orange tray icon and choose Restart.
- 4 · In the studio pick Hunyuan3D — it now runs on this machine's GPU, free.
Wants an NVIDIA GPU with 16 GB of memory for the densest grid; on a smaller card it steps down a size instead of failing. It generates geometry only — texture maps come from the premium engines.
Tripo's own weights: TripoSG
The model Tripo itself released as open weights: sharp surface detail from one frame, and no TRIPO_API_KEY or per-run fee. It installs in its own Python environment beside the other pipelines; the first run downloads about 12 GB of weights.
Download the TripoSG installer- 1 · Save install-triposg.bat in the same folder as start-maker-agent.bat.
- 2 · Double-click it and let it finish.
- 3 · Right-click the orange tray icon and choose Restart.
- 4 · In the studio pick TripoSG — or leave Auto on and the router uses it when it is the strongest engine online.
Wants an NVIDIA GPU with 12 GB of memory; on a smaller card it steps down a size instead of failing.
Fast: TripoSR (preview grade)
If a run stops with “no reconstruction pipeline”, the runner had nothing to call. TripoSR is quick and light, and its output stays soft on complex figures — keep it for quick previews. This installer sets it up with its own Python environment and points the agent at it.
Download the TripoSR installer- 1 · Save install-pipeline.bat next to start-maker-agent.bat and double-click it.
- 2 · When it says Done, right-click the orange tray icon and choose Restart.
- 3 · It reconstructs on this machine's GPU, still free.
- 4 · A portable Blender goes in with it, so a finished model is retopologised to your triangle budget and its detail baked — no separate Blender install.
doing it by hand
nvidia-smi # the GPU and its driver python --version # 3.10 or newer
TRELLIS, text or image to mesh (WSL2 recommended on Windows)
git clone --recurse-submodules https://github.com/microsoft/TRELLIS cd TRELLIS . ./setup.sh --new-env --basic --xformers --diffoctreerast --spconv --mipgaussian --kaolin --nvdiffrast set "MP_TRELLIS_SCRIPT=%CD%\example.py" set "MP_PYTHON=%CD%\.venv\Scripts\python.exe"
Already have a script of your own? Point the runner at it once — every later job uses it:
set "MP_LOCAL_SCRIPT=C:\path\to\run.py"
Those lines go in the machine's agent-config.bat, next to the agent. Restart it from the tray once, then start the generation again.
when it does not connect
The agent exits with “Set MP_AGENT_KEY”
The key is shown once when you register a machine. Register again on the network page for a fresh key and pass it as MP_AGENT_KEY.
The agent logs “Unknown agent key”
The key belongs to a different account or the agent was deleted. Register the machine again and restart the script.
No agent window is open — is it still running?
On Windows it has no window: look for the orange 3 in the notification area, next to the clock. Right-click it for the log, Restart and Stop. Double-clicking start-maker-agent.bat again reuses the saved key and commands.
The tray icon vanished after a restart
The agent adds itself to the Windows startup folder the first time it runs, so it should come back by itself at login. If the shortcut was removed, double-click start-maker-agent.bat again — the tray then has a Start with Windows toggle.
The machine shows offline on the dashboard
An agent is live only while it polls, roughly every five seconds. A laptop that sleeps drops off after five minutes. Restart the script and refresh the check below.
Jobs fail with “No mesh file is mirrored”
That model has no downloadable file on the platform yet. Models imported from a design page need their mesh uploaded before a machine can slice them.
Windows shows “Windows protected your PC” when the starter opens
That is SmartScreen meeting an unfamiliar file. Choose More info, then Run anyway. If your browser saved it as a .txt file, rename it to start-maker-agent.bat first.
The starter says Node.js is required
Install the LTS build from nodejs.org, close the window, and double-click the starter again. Nothing else has to be installed.
The command runs by hand but not through the agent
Quote the whole command, including any path with spaces, and use the full path to the tool: an agent started by a service manager does not inherit your shell PATH.
Nothing is claimed even though the agent is live
Check the machine's capabilities: processing-only agents never take generation work, and generation-only agents never take slicing work.
Machines keep 90% of every finished job and the remaining 10% is the platform fee. Earnings settle on the first of each month and show up on your earnings dashboard.
