Skip to content

Uai documentation

Uai runs parallel AI coding tasks in ephemeral dev containers, on runners you control.

The API reference is generated from the OpenAPI 3.1 description of the /api surface. Every endpoint lists its authentication, the permissions it requires, its parameters and every failure code it can return.

It is generated from the route definitions themselves rather than written by hand, so it cannot drift from the running service.

Payload shapes are a work in progress. Operations whose request and response bodies have been described show them in full; the rest say so on their own page rather than leaving you to guess, and are being filled in.

Every endpoint takes a bearer token: a session token from the app, or a user-scoped API key for CLI, MCP and headless clients. Workspace-scoped keys are rejected, API access is a paid feature, and most requests need to name a workspace.

Authentication covers all of it.