ComputerSchema. API detail: Computers.
create
POST /v1/computers. Every field is optional — an empty body gets the defaults.
string
Display name.
integer
Virtual CPUs.
integer
Memory in MiB.
integer
Disk in GiB.
object
Browser policy, e.g.
{ allowed_domains: ["*.example.com"] }.string
A
snp_ snapshot to restore from.list
GET /v1/computers, cursor-paginated.
get
GET /v1/computers/{id}.
exec
POST /v1/computers/{id}/exec. Runs a shell command and answers when it exits:
timeoutMs maps to the timeout_ms body field; the command is killed when it elapses.
pause / resume
POST /v1/computers/{id}/pause and POST /v1/computers/{id}/resume. Paused bills storage only — the first efficiency lever. Resume brings the same disk back.
snapshot
POST /v1/computers/{id}/snapshot. Captures the filesystem for fast restore; pass the returned snapshot_id to create.
fs
/v1/computers/{id}/fs/* routes — FsOp is "read" | "write" | "list" | "mkdir" | "remove". Splitting it would produce five near-identical methods with no added type safety. The reply differs per op ({content}, {entries}, {created}, …), so it comes back unparsed.
Every op takes an absolute path. read and write also take encoding ("text" default, "base64" for binary) and write takes content:
delete
DELETE /v1/computers/{id}. Destroys the machine and its disk. Snapshots survive.