---
title: Reference
description: Every capability the product ships, and the limits on each.
---

Everything below is a call the API answers today, reachable from both SDKs, the CLI and every
integration. Nothing here is planned or partial unless it says so.

## Driving a machine

<CardGroup cols={2}>
  <Card title="Machines" href="/docs/reference/machines" icon="server">
    Create, stop, start, fork and delete. Sizes, states and the event log.
  </Card>
  <Card title="The desktop" href="/docs/reference/desktop" icon="monitor">
    Screenshots, pointer, keyboard, clipboard and display geometry.
  </Card>
  <Card title="The terminal" href="/docs/reference/terminal" icon="terminal">
    One-shot commands as argv, and interactive ptys.
  </Card>
  <Card title="Files" href="/docs/reference/files" icon="folder">
    List, read, write, upload and download, with an explicit encoding.
  </Card>
  <Card title="The browser" href="/docs/reference/browser" icon="globe">
    Open a URL, enumerate tabs, drive the rest as a desktop.
  </Card>
  <Card title="Sessions and input control" href="/docs/reference/sessions" icon="users">
    One holder of the keyboard at a time, and how a person takes it back.
  </Card>
</CardGroup>

## Keeping and reaching a machine

<CardGroup cols={2}>
  <Card title="Snapshots, forks and templates" href="/docs/reference/persistence" icon="copy">
    Captured disks, branched machines and named starting states.
  </Card>
  <Card title="Published ports" href="/docs/reference/ports" icon="link">
    A guest port at its own https hostname, private by default.
  </Card>
  <Card title="Secrets" href="/docs/reference/secrets" icon="key">
    Values delivered into tmpfs, never readable back out.
  </Card>
  <Card title="The realtime gateway" href="/docs/reference/realtime" icon="zap">
    Live screen, input, terminal and event channels over one websocket protocol.
  </Card>
</CardGroup>

## The account around it

<CardGroup cols={2}>
  <Card title="Organizations, members and keys" href="/docs/reference/organizations" icon="shield">
    Roles, permissions, API key scopes and how they intersect.
  </Card>
  <Card title="Plans, usage and billing" href="/docs/reference/billing" icon="credit-card">
    Entitlements, meters, rates and the current-period summary.
  </Card>
  <Card title="API conventions" href="/docs/reference/api-conventions" icon="book-open">
    Auth, idempotency, pagination, ids and versioning, in one place.
  </Card>
  <Card title="Errors" href="/docs/reference/errors" icon="alert-triangle">
    The closed set of codes, what each means, and which are worth retrying.
  </Card>
</CardGroup>

## Not shipped yet

Two things are worth naming because their absence changes how you design around them.

- **Memory snapshots.** A capture is a cold disk capture and a start is a normal boot. There is
  no resume-from-RAM, so a long-running process does not survive a stop.
- **Portable snapshots.** A captured disk lives on one host. Object storage is declared in
  configuration but nothing writes to it yet.