Workspaces

A workspace is the tenancy boundary. It owns the data (memory, projects, conversations, artifacts), the billing balance that agent runs and generation spend, and the members and API keys. Almost every endpoint is scoped under one.

The scoping pattern

Resource endpoints live under the workspace, and your API key is bound to exactly one workspace:

text

/v1/workspaces/{workspace_id}/memory
/v1/workspaces/{workspace_id}/projects
/v1/workspaces/{workspace_id}/conversations
/v1/workspaces/{workspace_id}/agent/runs
/v1/workspaces/{workspace_id}/api-keys

Find your workspace_id (a UUID) in the app URL — /app/{workspace_id}/… — and in Settings.

Reading a workspace

GET/v1/workspaces/{workspace_id} —

the workspace (name, plan, your role).

POST/v1/workspaces —

create a new workspace (usually done in the app).

bash

curl https://nexevo.ai/v1/workspaces/$NEXEVO_WORKSPACE \
  -H "Authorization: Bearer $NEXEVO_API_KEY"

Members & invites

Workspaces have members with roles (owner / admin / member / viewer). Members are added by invite link, and roles gate who can manage settings, billing, and destructive actions. For programmatic integrations you typically use an API key rather than a member session — see Authentication.

Billing is per-workspace: agent runs, generation, and cloud-desktop time draw down the workspace balance. A run is gated by both budget_usd (a per-run ceiling) and the workspace balance.