Overview
SDKs, CLI, and HTTP API reference for driving a Fuse orchestrator
This section is the reference for driving a running Fuse orchestrator: the three client SDKs, the operator CLI, and the raw HTTP API underneath both. If you’re new to Fuse’s concepts, start with Concepts first. This section assumes you already know what an environment, host, and snapshot are.
Picking a surface
CLI
The fastest way to operate Fuse by hand: register hosts, bring up environments, inspect and tear things down.
SDKs
Drive Fuse programmatically from your own service or agent harness. Go, Python, and TypeScript, all mirroring the same shape.
HTTP API
The raw REST surface every SDK and the CLI itself are built on.
Authentication
How the orchestrator authenticates callers, across the CLI, SDKs, and browser.
Resource coverage
Every surface exposes the same four resources:
| Resource | What it manages |
|---|---|
| Environments | Create, list, inspect, drain, fork, destroy microVMs. |
| Hosts | Register, list, cordon/uncordon, remove compute hosts. |
| Snapshots | Create, list, restore, delete VM snapshots. |
| API keys | Issue and revoke orchestrator-global API keys (master-token only). |