Skip to main content
Start with the API quickstart to make an authenticated request. Endpoint pages render their request and response contracts from checked-in OpenAPI specifications and retain Mintlify’s native playground.

​
Choose a resource

  • Workspaces: lifecycle and resources.
  • Apps: installed applications and runtime controls.
  • App releases: prepare and activate v0.13 deployments.
  • Local tunnels: HTTPS access to a local service, with private, invited, or public sharing.
  • Snapshots: stopped-workspace root-disk checkpoints.
  • API keys: account credentials.

​
Separate interfaces

The account API uses the public HTTPS endpoint and an authorized credential. The managed AI proxy is a VM-local interface with different authentication and protocol semantics. First-party console and policy endpoints are grouped separately from the application deployment lifecycle. This is a v0.13 documentation preview. App-release functionality requires the matching server capability. Reading a generated schema does not establish that a feature is enabled for your account. See API conventions for polling, pagination, and failure handling. The tunnel API pages are reference-only and do not offer a live request playground. Use the signed CLI 0.13.1 or later to run a connector, and read the exposure and shared-browser-site risks before sharing an app.