Standalone starter apps

Templates that invert an owned still with one generate call over HTTP, MCP, the CLI or an SDK.

Updated

Teaching journey

Each starter uploads a still, then calls the generate tool once with a small inline Comfy graph, LoadImage → ImageInvert → SaveImage, and its request_id. It follows the job with read of wm://job/{id} and cancels with write and {"uri": "wm://job/{id}", "cancel": true}. The Python, Go, CLI, MCP and HTTP starters journal dispatching before they call generate and refuse to send a second invert while that journal entry is uncertain. They teach request identity and recovery: one run dispatches once, and after a crash or timeout the starter reads the original job instead of sending another.

Templates

  • Node web: a single-user loopback UI. The key stays on the server and the browser never sees it. It binds 127.0.0.1 only, and refuses hostile Host, Origin and CSRF requests before any upstream call.
  • Python worker: the Python client and a crash-safe journal with invert, inspect, resume and cancel.
  • Go worker: the Go client with the same commands.
  • CLI: the installed wavemaker executable: wavemaker files upload, then wavemaker api call generate --file … --request-id ….
  • MCP: the tools over Streamable HTTP MCP. The still goes up with write and content_base64.
  • HTTP: plain POST /v1/tools/{tool} calls, a hash-checked upload and a hash-verified download.

Public templates are not published yet. Until they are, follow the HTTP API or MCP guides directly.

SDKs · CLI · HTTP · MCP

Related guidance